ci: use --frozen-lockfile in the publish version bump#180
Merged
JohnMcLear merged 1 commit intomasterfrom Apr 17, 2026
Merged
Conversation
The publish workflow ran a plain `pnpm i` before `pnpm version patch`. If the lockfile was even slightly out of sync with package.json (easy to happen when a dependency bump is merged via PR), that install updated pnpm-lock.yaml and left the working tree dirty. `pnpm version patch` silently declines to create a git tag in a dirty tree but still writes the new version into package.json, and the subsequent `git push --atomic <branch> vX.Y.Z` fails with: error: src refspec vX.Y.Z does not match any — blocking the publish. Using `--frozen-lockfile` keeps the tree clean; if the lockfile really is out of sync, the install fails loudly (which is what we want — the fix is to update the lockfile in a PR, not silently during publish). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The publish workflow ran plain
pnpm ibeforepnpm version patch. If the lockfile was slightly out of sync, that install updated pnpm-lock.yaml and left the tree dirty;pnpm version patchsilently skipped creating the git tag but still wrote the new version into package.json, and the subsequentgit push --atomic <branch> vX.Y.Zfailed withsrc refspec vX.Y.Z does not match any. Using--frozen-lockfilekeeps the tree clean so the tag gets created.