fix(ci): pair changesets CLI v3 with changesets/action v2 - #330
Merged
Merged
Conversation
#322 bumped changesets/action 1 -> 2 on its own, which broke every publish on main: Error: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported; use Changesets action v1 instead, which is compatible with CLI v2. The action and the CLI are a matched pair, so the CLI has to move with it. #325 is the other half of #322 and should have landed together. Action v2 also renamed the input: publish: -> publish-script: which the run logged as a warning rather than an error, so the step would have silently done nothing even once the CLI matched. Verified against v3 locally: `changeset status --since=origin/main` and `changeset publish --help` both work, and `changeset version` produces the expected 3.2.1 -> 3.2.2 bump and changelog from the pending test-tmp-race changeset (bump reverted here; the release PR is the action's job). Closes #325. Config `$schema` follows @changesets/config to 4.0.0.
keonik
added
the
skip-changeset
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.
The release path on
mainis currently broken. Every push to main now fails the Publish workflow, and the pending release PR (#321) is stale because of it.What happened
#322 bumped
changesets/action1 → 2 by itself. The action and the CLI are a matched pair:#325 —
@changesets/cli2.x → 3.0.1 — is the other half of #322. They needed to land together. I earlier suggested closing #325 and letting Dependabot re-raise it; that was wrong, and this PR carries it instead.A second, quieter break
Action v2 renamed the input. This was logged as a warning, not an error:
So even once the CLI matched, the publish step would have run with no publish script configured and silently created release PRs without ever publishing. Fixed here too:
Verification against v3 locally
bunx changeset status --since=origin/main— works (still the CI gate's command)bunx changeset publish --help— works; no--accessflag, consistent with fix(ci): drop the --access flag that broke the 3.0.1 publish #308bunx changeset version— correct3.2.1→3.2.2bump and changelog from the pendingtest-tmp-racechangeset. Bump reverted in this branch — generating the release PR is the action's job, not this PR's.bun run build,bun run test(37/37 files, 70 passed, 1 skipped),lint,format:check— all cleanbun.lockshrinks ~140 lines: changesets v3 collapses the@changesets/*constellation (apply-release-plan,assemble-release-plan,get-release-plan, …) into far fewer packages..changeset/config.json$schemafollows@changesets/configto 4.0.0.Closes #325.
Not fixed here
The Dependabot
bunrun is failing for an unrelated upstream reason — see my comment on #329's follow-up. Separate problem, separate fix.