chore: upgrade Changesets to CLI v3 and action v2 - #66
Conversation
Action 2.1.0 requires Changesets CLI v3 and renamed inputs. We still ship CLI 2.31, so Release fails on every main push. Restore the v1 pin and ignore major action bumps until the CLI moves.
Action 2.1.0 on main is incompatible with CLI 2.31. Take CLI 3.0.1, changelog-github 1.0.0, and action v2.1.1 with the renamed inputs. Custom publish writes CHANGESETS_OUTPUT so tags and GitHub releases still land.
|
|
Warning Review limit reachedNext included review available in 15 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
@changesets/cli3.0.1 +@changesets/changelog-github1.0.0.changesets/action@v2.1.1withversion-script/publish-script/pr-title/commit-message/create-github-releases.scripts/release.tswritesCHANGESETS_OUTPUTgit-tagevents so action v2 can push tags and create GitHub releases (stdoutNew tag:is no longer read).ignoreworkaround).Replaces #65 (GitHub closed it when the branch was renamed).
Test plan
bunx changeset statusruns under CLI 3chore: version packages