feat: migrate release tooling to Changesets v3 - #663
Merged
Conversation
creatornader
force-pushed
the
migrate/changesets-v3-20260824
branch
from
August 24, 2026 22:32
85e081b to
0ba57c9
Compare
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.
Completes the planned Changesets v3 migration after the release outage was restored by #662. Upgrades @changesets/cli to 3.0.1, migrates changesets/action v2 inputs, preserves GitHub API signing through the release App, removes the obsolete read-yaml-file patch and temporary Dependabot hold, adds a release contract check to CI, and verifies snapshot versioning with the custom changelog formatter. Local validation passed: workspace build, typecheck, full tests, lint, doc-sync, and contract checks.