Repository navigation
Conversation
|
@ArekChr is attempting to deploy a commit to the Callstack Team on Vercel. A member of the Team first needs to authorize it. |
|
ArekChr
marked this pull request as ready for review
October 19, 2026 08:10
This branch has not been deployed
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.
Summary
Changesets currently creates a GitHub release for every published package. Create one combined release on the existing main package tag instead, with notes collected from all packages in the fixed release group.
Validation
node --test .github/scripts/*.test.mjs— 18 tests passed, including 5.4.2 notes, one release for six packages, existing releases, and retry behavior..github/scriptsandpackage.json— passed.git diff --check— passed.Scope
This covers the current fixed group containing
@callstack/repack. Missing or mismatched package tags require manual verification and repair before retrying; the script does not recover npm publications or recreate tags. Canary publishing is unchanged.