chore(deps-dev): migrate changesets to v3 - #2222
Merged
Merged
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
kuhe
approved these changes
Aug 13, 2026
siddsriv
approved these changes
Aug 13, 2026
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
3 participants
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.
Issue #, if available:
https://changesets.dev/blog/announcing-changesets-v3
Description of changes:
Upgrade @changesets/cli to v3 and changesets/action to v2, which is the version of the action compatible with Changesets v3.
The v3 config needed no changes beyond the schema pin, which now points at the copy in node_modules so it tracks the installed version.
access: "public"is still valid, andbaseBranchandprivatePackagesnow match v3's defaults; they are kept becausenpm-package-existence.ymlcitesprivatePackages.versionby name.The v2 action renames its inputs and outputs: version, publish, commit and title become version-script, publish-script, commit-message and pr-title, and pullRequestNumber becomes pr-number. It also no longer reads the GITHUB_TOKEN environment variable, so the token is passed through the github-token input. Its branching is unchanged, so both release workflows behave as before.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.