Migrate releases to Changesets v3 - #57
Merged
Merged
Conversation
Keep the reusable release workflow compatible with the current Changesets CLI and Action contract while preserving GitHub App authentication for release operations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Keep the production dependency audit green after the nanoid denial-of-service advisory. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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.
Summary
@changesets/clito v3 and use the matching v4 configuration schemachangesets/action@v1.9.0to the SHA-pinned v2.1.1 contractgithub-tokenand use the renamed script, commit, and PR inputschangeset git-tagcommand for tag-only consumersCompatibility
Consumers must upgrade to
@changesets/cli@^3and renamechangeset tagtochangeset git-tagbefore repinning the reusable workflow to this revision. Existing SHA-pinned consumers remain unchanged.No changeset is required because this only changes workflows, documentation, and root tooling.
Checks
pnpm code-reviewchangeset statuswith CLI v3.0.1