Skip to content

chore: upgrade packageManager to pnpm@11.9.0#875

Open
panish16 wants to merge 6 commits into
bcgov:mainfrom
panish16:feat/upgrade-pnpm-v11
Open

chore: upgrade packageManager to pnpm@11.9.0#875
panish16 wants to merge 6 commits into
bcgov:mainfrom
panish16:feat/upgrade-pnpm-v11

Conversation

@panish16

Copy link
Copy Markdown
Contributor

Sets packageManager to pnpm@11.9.0 in app/package.json as part of the pnpm v11 upgrade (ticket #33875).

The Cloud Build CI trigger has already been updated to use pnpm@11.9.0.

panish16 and others added 5 commits June 25, 2026 15:40
…asInjectionContext not available in vue-demi v2 mode)
pnpm v11 stopped reading package.json's "pnpm" key, silently dropping
the sbc-common-components patch and build-script approvals and
causing a lockfile mismatch. Move both to pnpm-workspace.yaml and
regenerate the lockfile (which also fixes a stale pinia resolution:
package.json already pinned ~2.0.35 for Vue 2 compatibility, but the
committed lockfile still resolved 2.3.1).
…mpat

The production linting-pnpm (24, 9) job still runs pnpm 9, which
requires a non-missing "packages" field in any pnpm-workspace.yaml it
finds ("ERROR packages field missing or empty"), even though this file
exists purely for pnpm 11's allowBuilds/patchedDependencies settings.
Declare packages: [] explicitly so both pnpm versions handle the file.
The shared bcregistry-sre/frontend-ci.yaml workflow defaults
pnpm_version to "9" when unset, and pnpm/action-setup doesn't defer to
packageManager for that bare default. Pin pnpm_version to 11.9.0
explicitly, matching packageManager, as a stopgap until
bcgov/bcregistry-sre#369 lands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant