Skip to content

Rename changesets/action inputs for v2 so the release workflow runs again - #687

Merged
mikeallisonJS merged 1 commit into
mainfrom
fix-changesets-action-v2-inputs
Oct 15, 2026
Merged

mikeallisonJS merged 1 commit into
mainfrom
fix-changesets-action-v2-inputs

Conversation

@mikeallisonJS

@mikeallisonJS mikeallisonJS commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

Why

Every release run on main has failed since #653 bumped changesets/action from v1 to v2.1.2. The v2 action renamed its root inputs and refuses the old names:

##[error]The following inputs have been renamed:
- "publish" -> "publish-script"
- "version" -> "version-script"
- "commit" -> "commit-message"
- "title" -> "pr-title"
Please update your workflow file.

So no Version Packages PR has been opened or updated, and nothing has published, for the last dozen merges.

What

Renames the four inputs in .github/workflows/release.yml. Nothing else changes:

  • The published output keeps its name in v2, so the step that pushes the vX.Y.Z tag is untouched.
  • v2 requires Changesets CLI v3, which Update dependency @changesets/cli to v3 #654 already landed. None of the v3 breaking changes touch changeset version or changeset publish as this repo calls them, and privatePackages is already set explicitly in .changeset/config.json.
  • Publish auth was already trusted publishing, which is what v2 expects.

CI-only, so this carries skip-changeset.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated release workflow configuration; release commands and messaging remain unchanged.

PR #653 moved the release workflow from changesets/action v1 to v2.1.2,
which renamed its root inputs. The action now rejects the old names, so
every push to main since has failed before versioning or publishing.

  version -> version-script
  publish -> publish-script
  commit  -> commit-message
  title   -> pr-title

The `published` output keeps its name, so the follow-on tag step is
untouched. The CLI is already on v3 (#654), which v2 of the action
requires.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@mikeallisonJS mikeallisonJS added the skip-changeset No release note needed: docs-, CI-, or test-only. Skips the changeset gate. label Oct 15, 2026
@github-actions github-actions Bot added the vouch:trusted Author is trusted by repo permissions or the VOUCHED list. label Oct 15, 2026
@coderabbitai

coderabbitai Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository: JesusFilm/phoebe/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: a0e75c5f-8540-4845-b147-5854e2fdea2a
📥 Commits

Reviewing files that changed from the base of the PR and between 82e35a3 and 9c0baf8.

📒 Files selected for processing: 1
  • .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The release workflow renames four Changesets action input keys. Their configured values remain unchanged.

Changes: Release workflow

Layer / File(s) Summary
Changesets action inputs
.github/workflows/release.yml
The workflow replaces version, publish, commit, and title with version-script, publish-script, commit-message, and pr-title. The configured values do not change.

Priority: ⬆️ High

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 9c0ba

The workflow now uses the action’s supported input names while preserving its configured commands and publish-tag step. No actionable merge-blocking risk remains.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main change: renaming changesets/action inputs for v2 so the release workflow can run again.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mikeallisonJS
mikeallisonJS merged commit 545d754 into main Oct 15, 2026
6 of 7 checks passed
@mikeallisonJS
mikeallisonJS deleted the fix-changesets-action-v2-inputs branch October 15, 2026 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changeset No release note needed: docs-, CI-, or test-only. Skips the changeset gate. vouch:trusted Author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant