Regenerate the lockfile with the pinned pnpm - #6
Merged
Merged
Conversation
The refactor was installed with a global pnpm 8, which rewrote the lockfile as v6. CI runs the pinned pnpm 10 and refuses a v6 lockfile under --frozen-lockfile. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
CI on main failed at
pnpm install --frozen-lockfilewithERR_PNPM_LOCKFILE_BREAKING_CHANGE. #5 was installed with a global pnpm 8.10.4, which rewrotepnpm-lock.yamlfrom lockfile v9 to v6; CI uses the pinnedpnpm@10.34.5and rejects it.Regenerated with
pnpm@10.34.5. Verified locally:install --frozen-lockfilepasses, 50/50 tests pass.🤖 Generated with Claude Code