ci: use the input names changesets/action v2 expects - #4838
Conversation
v2 renamed every input this workflow passes, so the release job has failed since the action was bumped in #4831: `version` is `version-script`, `publish` is `publish-script`, `commit` is `commit-message` and `title` is `pr-title`. Note the action's own error message misspells one of them as `commit-mesage`; `action.yml` at the pinned commit spells it `commit-message`, and taking the error at its word would silently restore the default "Version Packages" commit message.
|
|
This PR is packaged and the instant preview is available (1f6593a). Install it locally:
npm i -D create-webpack-app@https://pkg.pr.new/create-webpack-app@1f6593a webpack-cli@https://pkg.pr.new/webpack-cli@1f6593a
yarn add -D create-webpack-app@https://pkg.pr.new/create-webpack-app@1f6593a webpack-cli@https://pkg.pr.new/webpack-cli@1f6593a
pnpm add -D create-webpack-app@https://pkg.pr.new/create-webpack-app@1f6593a webpack-cli@https://pkg.pr.new/webpack-cli@1f6593a |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4838 +/- ##
==========================================
- Coverage 94.95% 94.80% -0.15%
==========================================
Files 14 14
Lines 5406 5406
Branches 802 799 -3
==========================================
- Hits 5133 5125 -8
- Misses 272 280 +8
Partials 1 1 see 3 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
1 participant
Summary
The Release workflow has failed on every push to
mainsince #4831 bumpedchangesets/actionto v2, which renamed every input the workflow passes and errors out rather than ignoring the old ones:version→version-script,publish→publish-script,commit→commit-message,title→pr-title. Run 121 (11 Aug) was the last success.Worth noting for review: the action's own error message misspells one of them as
commit-mesage.action.ymlat the pinned commit spells itcommit-message, and taking the error at its word would silently fall back to the defaultVersion Packagescommit message. The one output this workflow consumes,steps.changesets.outputs.published, is unchanged in v2.What kind of change does this PR introduce?
ci
Did you add tests for your changes?
No — a workflow input rename that no test can exercise. Each name was checked against
action.ymlat the pinned commit198f833, and the file was verified to parse with the four inputs set as intended. It proves itself on the next push tomain, since the workflow has no manual trigger.Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
n/a — though note that seven releases have been skipped while this was broken, so the first successful run will open a version PR covering everything accumulated since 11 Aug.
Use of AI
Claude Code was used to read the failing job log, trace the breakage back to the run that introduced it, check the input names against the pinned action's
action.yml(catching the typo in the error message), and apply the rename. The change was reviewed before committing.Generated by Claude Code