chore: upgrade packageManager to pnpm@11.9.0#343
Conversation
panish16
force-pushed
the
feat/upgrade-pnpm-v11
branch
from
2f7ee67 to
b894dab
Compare
package.json still had packageManager pinned to pnpm@10.17.1 even though ci.yml already requests pnpm_version: latest-11. Once the shared frontend-ci workflow prefers packageManager over the input (bcgov/bcregistry-sre#369), this repo would have silently kept running on pnpm 10.17.1 instead of pnpm 11.
|
Caught something worth flagging while testing bcgov/bcregistry-sre#369 (the shared frontend-ci workflow update): Right now that doesn't matter since the current shared workflow just uses the Pushed a fix: pinned |
- version: latest-11 is a floating tag; it just moved to 11.12.0 and hit a pnpm/action-setup self-install bug (Cannot use 'in' operator to search for 'integrity' in undefined). Pinned to 11.9.0 to match packageManager. - plain pnpm install fails under pnpm 11 with ERR_PNPM_IGNORED_BUILDS since this repo has no approved-builds config. Added --ignore-scripts plus an explicit nuxt prepare step, matching the shared frontend-ci workflow's approach. Verified locally end to end (install, prepare, build all exit 0).
|
/gcbrun |
1 similar comment
|
/gcbrun |
2 participants
Sets
packageManagertopnpm@11.9.0inweb/pay-ui/package.jsonas part of the pnpm v11 upgrade (ticket #33875).The CI/CD Cloud Build trigger for this app has already been updated to use
pnpm@11.9.0.