Repository navigation
chore(release): changesets cli v3 + changesets/action v2 inputs, unblock the release pipeline - #617
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 29 minutes. View limit details
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 |
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.
No
chore: version packagesPR has opened since #324 (August). Thereleasejob dies inchangesets/action:Dependabot moved
changesets/action1.9.0 to 2.0.0 (#551) and 2.1.2 (#603). v2 requires@changesets/cliv3 and renamed its inputs; the repo stayed on CLI 2.31.0 with the v1 input names, so every release run since August failed (when it was not cancelled bycancel-in-progressor stuck behind thenpm-publishenvironment approval).Change
@changesets/cli2.31.0 to 3.0.3,@changesets/changelog-github0.7.0 to 1.0.1,@changesets/parse0.4.3 to 1.0.0 (packages/publish). Lockfile: only@changesets/*and their transitive deps move (prettier, js-yaml, fs-extra and friends drop out)..changeset/config.json:privatePackages: {version: true, tag: false}. v3 stops versioning private packages by default;@conciv/app(ships inside@conciv/embed), the site, examples and e2e apps keep bumping in lockstep with the fixed@conciv/*group as they did under v2.release.yml: the step keeps the pinned v2.1.2 sha; inputs becomeversion-script,publish-script,commit-message,pr-title;commitModeandsetupGitUserare gone (v2 pushes through the GitHub API by default,github-tokendefaults togithub.token).conciv-publish sync:changeset tagwas renamedchangeset git-tagin v3.cli.test.ts:@changesets/parse1.0 parses YAML withyamlinstead ofjs-yaml, so the duplicate-key error reads "Map keys must be unique"; the assertion follows.Verification
changeset --version3.0.3;changeset statuslists every pending package.changeset version(then reverted): 252 files, every changeset consumed,@conciv/core,@conciv/appand@conciv/publishall at 0.0.20.@conciv/publishtests 72/72, typecheck,check-changesets --require-coverage, fallow audit pass, lint, format.After merge
The push to main starts a release run that waits on the
npm-publishenvironment. Approving it runschangesets/action, which opens the version PR; merging that publishes 0.0.20.🤖 Generated with Claude Code