fix(build): approve pnpm 11 build scripts for native deps#4643
Conversation
pnpm was upgraded to v11 (via `npm install -g pnpm` in the Dockerfile), which now blocks build scripts for native packages by default. - Add pnpm-workspace.yaml with allowBuilds for @parcel/watcher, esbuild, and sharp (generated via `pnpm approve-builds --all`) - Update Dockerfile COPY to include pnpm-workspace.yaml so the approval file is available during the Docker build
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Fixes the pnpm 11 Unpinned pnpm version (root cause not addressed)
Silent maintenance burden from allowlist The |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4643 +/- ##
=======================================
Coverage 92.52% 92.52%
=======================================
Files 359 359
Lines 10791 10791
Branches 821 821
=======================================
Hits 9984 9984
Misses 696 696
Partials 111 111 🚀 New features to boost your workflow:
|
Summary
[ERR_PNPM_IGNORED_BUILDS]becausenpm install -g pnpmin the Dockerfile now installs pnpm v11, which blocks build scripts for native packages by default (a security change introduced in pnpm 10+)@parcel/watcher,esbuild, andsharppnpm-workspace.yamlwithallowBuilds(generated viapnpm approve-builds --all) and update the DockerfileCOPYto include itChanges
backend/custom_admin/pnpm-workspace.yaml— new file, pnpm 11's approval mechanism for native build scriptsbackend/Dockerfile— copypnpm-workspace.yamlinto the Docker build context alongsidepackage.jsonandpnpm-lock.yamlTest plan
Build backendCI job passes on this PR