Skip to content

chore: upgrade packageManager to pnpm@11.9.0#2343

Merged
eve-git merged 4 commits into
bcgov:mainfrom
panish16:feat/upgrade-pnpm-v11
Jul 9, 2026
Merged

chore: upgrade packageManager to pnpm@11.9.0#2343
eve-git merged 4 commits into
bcgov:mainfrom
panish16:feat/upgrade-pnpm-v11

Conversation

@panish16

Copy link
Copy Markdown
Contributor

Sets packageManager to pnpm@11.9.0 in ppr-ui/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 4 commits June 25, 2026 10:48
pnpm v11 stopped reading package.json's "pnpm" key; move build-script
approvals to pnpm-workspace.yaml (with an explicit empty packages list,
since the production lint job's older pnpm still requires that field
to be present) and drop the now-dead empty overrides block.
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.
@eve-git eve-git self-requested a review July 9, 2026 20:52
@eve-git

eve-git commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

/gcbrun

@bcregistry-sre

Copy link
Copy Markdown
Collaborator

Temporary Url for review: https://bcregistry-assets-dev--pr-2343-j0hw2g10.web.app

@eve-git eve-git merged commit e6fbfb2 into bcgov:main Jul 9, 2026
9 checks passed
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.

3 participants