Refresh pnpm lockfile in release PRs#1226
Merged
Merged
Conversation
aswamy
approved these changes
Jun 5, 2026
EvilGenius13
approved these changes
Jun 8, 2026
Changesets updates package manifests during release PR generation, but pnpm also tracks workspace dependency specifiers in pnpm-lock.yaml. Run a lockfile-only install after versioning so the release branch includes the matching lockfile instead of failing CI after merge.
graygilmore
force-pushed
the
gg-bump-lockfile-in-release-pr
branch
from
c6ef2ff to
48edd4c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the release orchestrator so generated Changesets release PRs refresh
pnpm-lock.yamlafterchangeset version.Why
The first release attempt after the pnpm migration bumped package manifests but left
pnpm-lock.yamlwith old workspace specifiers, sopnpm install --frozen-lockfilefailed after merge. pnpm stores workspace dependency specifiers in the lockfile, so the generated release PR needs to include that diff too.