Repository navigation
fix(fork): the release build regenerates the lockfile a merge changed - #33
Merged
Merged
Conversation
Since upstream's nightly conflicts in pnpm-lock.yaml, every Fork release failed with ERR_PNPM_OUTDATED_LOCKFILE: resolve-merge.sh takes upstream's lockfile and expects `vp install` to add the fork's dependencies (koffi), but pnpm freezes the lockfile under CI. It now installs with --no-frozen-lockfile. Co-Authored-By: Claude Opus 5.5 <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
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.
Every
Fork releasesince 2026-11-05 (latest red run 42233693866) failed after the merge conflicts were resolved:resolve-merge.shtakes upstream'spnpm-lock.yamland relies onvp installto add the fork's dependencies (koffi), but pnpm freezes the lockfile underCI, so the install stopped withERR_PNPM_OUTDATED_LOCKFILE.The script now runs
vp install --no-frozen-lockfile; the regenerated lockfile is committed into the build merge as before, so the build jobs' frozen install matches it.fork/resolve-merge.test.shruns withCI=trueand itsvpstub refuses a frozen install, so all five cases fail without the fix and pass with it.Done by Claude Opus 5.5 in Claude Code (T3 Code).
🤖 Generated with Claude Code