fix(release): validate lockfile before publishing - #368
Merged
Merged
Conversation
|
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.
The 9.8.2 release published both npm packages before checking the final workspace lockfile. Bun left local dependency references at 9.8.1, so the release stopped after publication and before its Git tag and GitHub release. This PR bumps and validates all release manifests before publishing, synchronizes only local workspace references that Bun leaves stale, and keeps the final Git and GitHub steps after publication. It also tests the preflight failure path and pins the CI Bun version to the declared package-manager version.
Reproduction
In the 9.8.2 release, both package publications succeeded. The final lockfile check then found three workspace dependency entries still at 9.8.1 even though their manifests had been bumped to 9.8.2.