Repository navigation
fix: revert changesets/action to v1 - #342
Merged
Merged
Conversation
Renovate bumped changesets/action to v2.1.2 in #340, which broke the release workflow on main. Action v2 requires Changesets CLI v3, but this repo pins @changesets/cli 2.31.0, so the action exits immediately: This version of the Changesets action is designed to work with Changesets CLI v3. Changesets CLI v2 is not supported. v2 also renamed every input, so commit, title, publish and createGithubReleases were all silently ignored. Most importantly publish (now publish-script) was unset, which would have downgraded the job to version-PR-only and skipped publishing to npm entirely. Revert to v1 and hold the major in Renovate until the CLI upgrade and input renames are done together. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
commit: |
abstrakt8
pushed a commit
that referenced
this pull request
Sep 25, 2026
The two have to move together. Action v2 refuses CLI v2 (#340, reverted in #342), and action v1 can't handle CLI v3: v1 finds what was published by matching `New tag:` in the publish output, which v3 no longer prints. Releases would still reach npm, but no git tags would be pushed and no GitHub releases created. - Bump @changesets/cli to 3.0.3 and changesets/action to v2. - Rename the action inputs for v2 (commit-message, pr-title, publish-script, create-github-releases). v2.1.2 fails on the old names. - Drop the GITHUB_TOKEN env from the release step. v2 takes the token from its github-token input (the default GitHub token), passes it to the publish script itself, and fails if the env var differs. - Remove the Renovate hold on changesets/action. - Point .changeset/config.json's $schema at @changesets/config 4.0.1, the version CLI v3 uses. The config validates against it unchanged. Action v2 reads the published packages from an NDJSON file named by CHANGESETS_OUTPUT. Verified locally that the variable reaches the CLI through `pnpm -w changeset`, that `changeset publish-plan` works against npm with pnpm 12, and that `changeset version` produces the same version bumps and changelog entries as CLI v2 for the pending changeset. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Fixes the Changesets workflow failure in run 34214808539.
What broke
#340 bumped
changesets/actionfromv1tov2.1.2. That's a major bump, and nothing else was migrated with it.1. Hard failure — action v2 requires Changesets CLI v3. This repo pins
@changesets/cli2.31.0, so the action exits before doing any work:2. Latent failure — v2 renamed every input, so all four in the workflow were silently ignored (the
Unexpected input(s)warning in the run):commitcommit-messagetitlepr-titlepublishpublish-scriptcreateGithubReleasescreate-github-releasespublish→publish-scriptis the one that matters: unset, the action falls back to version-PR-only mode. Had the CLI check passed, this job would have opened a "Version Packages" PR and never published to npm — a silent release regression rather than a red X.This PR
changesets/action@v1, which is still maintained on the action'smaintenance/v1branch (currently v1.9.0) and is the version compatible with CLI v2.Follow-up
The real migration is worth doing as its own PR, where a failed publish is visible rather than landing as a hotfix on a broken
main:@changesets/cli2.31.0 → 3.0.2.changeset/config.jsonagainst the newer config schema🤖 Generated with Claude Code