fix: sync lockfile after changeset version bump#763
Merged
Conversation
The changeset release PR was failing CI because `bun.lock` was not updated after `changeset version` bumped package versions. Add `bun install --no-frozen-lockfile` to the version script so the lockfile is regenerated and committed with the release PR. Co-Authored-By: Claude Opus 4.6 <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.
Summary
bun.lockwas not updated afterchangeset versionbumped package versionsbun install --no-frozen-lockfileto theversionscript so the lockfile is regenerated and committed with the release PRTest plan
bun.lockand pass--frozen-lockfilechecks🤖 Generated with Claude Code