From 678ce1128c37ddfca6d9c1a30139e0930617b4bb Mon Sep 17 00:00:00 2001 From: Thomas Jung Date: Wed, 11 Nov 2026 15:32:43 -0500 Subject: [PATCH] fix(deploy): move patch-package to dependencies so postinstall survives prod prune MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CF stages tutorials-srv with NODE_ENV=production, which prunes devDependencies. The postinstall hook runs `patch-package` (added in #3107 to apply patches/cds-caching+2.1.0.patch, a runtime dependency), but patch-package itself was only in devDependencies — so the prod prune removed the binary and staging failed with: npm error command sh -c patch-package npm error sh: 1: patch-package: not found (code 127) **ERROR** Unable to build dependencies: exit status 127 BuildpackCompileFailed Moving patch-package to dependencies keeps the binary in the pruned prod tree so the postinstall completes and the cds-caching patch applies at staging time. cds-caching is itself a runtime dependency, so the patch must apply in the production install. Broke the 2026-11-11 DEV deploy (tutorials-srv staging, all 3 retries). --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 565adfc55..e21afc705 100644 --- a/package.json +++ b/package.json @@ -169,7 +169,6 @@ "esbuild": "0.28.2", "fundamental-styles": "^0.41.7", "happy-dom": "20.14.3", - "patch-package": "8.0.1", "playwright-core": "^1.61.1", "postcss": "^8.5.16", "postcss-cli": "^11.0.1", @@ -240,6 +239,7 @@ "node-sql-parser": "^5.4.0", "nodemailer": "9.0.3", "passport": "^0.7.0", + "patch-package": "8.0.1", "qrcode": "^1.5.4", "sharp": "0.35.3", "socket.io": "^4.8.3",