Repository navigation
Rename changesets/action inputs for v2 so the release workflow runs again - #687
Conversation
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>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Why
Every
releaserun on main has failed since #653 bumpedchangesets/actionfrom v1 to v2.1.2. The v2 action renamed its root inputs and refuses the old names: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:publishedoutput keeps its name in v2, so the step that pushes thevX.Y.Ztag is untouched.changeset versionorchangeset publishas this repo calls them, andprivatePackagesis already set explicitly in.changeset/config.json.CI-only, so this carries
skip-changeset.🤖 Generated with Claude Code
Summary by CodeRabbit