Update changesets/action action to v2 - #733
renovate[bot] wants to merge 1 commit into
Conversation
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| - name: Create Release Pull Request or Publish to npm | ||
| id: changesets | ||
| uses: changesets/action@6a0a831ff30acef54f2c6aa1cbbc1096b066edaf # v1.7.0 | ||
| uses: changesets/action@8488615a623b1b9c987934bb89eae8af6a946ac1 # v2.1.1 |
There was a problem hiding this comment.
🔴 Release workflow rejects installed CLI
Every release run makes changesets/action@v2 reject the installed @changesets/cli v2 dependency. Version PR creation and npm publication both stop.
Learn more
Changesets Action v2 validates the root package before selecting version or publish mode. The root package declares @changesets/cli as ^2.31.0, and the lockfile resolves that major version. Action v2 rejects any Changesets CLI v2 installation, so this job exits before processing changesets.
Example: A push to main with a new changeset starts build_and_release. The action reports that Changesets CLI v2 is unsupported instead of opening the version PR.
Recommended fix: Upgrade @changesets/cli and its lockfile entry to a compatible v3 release, including any required configuration migrations, before adopting Changesets Action v2.
Was this helpful? React with 👍 or 👎 to provide feedback.
| - name: Create Release Pull Request or Publish to npm | ||
| id: changesets | ||
| uses: changesets/action@6a0a831ff30acef54f2c6aa1cbbc1096b066edaf # v1.7.0 | ||
| uses: changesets/action@8488615a623b1b9c987934bb89eae8af6a946ac1 # v2.1.1 |
There was a problem hiding this comment.
🔴 Renamed publish input aborts releases
After the CLI upgrade, changesets/action@v2 rejects the obsolete publish input. Version PR creation and npm publication remain disabled.
Learn more
Changesets Action v2 intentionally checks for v1 input names and throws when it finds one. This workflow still supplies publish, while v2 accepts the custom command through publish-script. The CLI validation currently fails first, but correcting the CLI alone exposes this second unconditional failure.
Example: With Changesets CLI v3 installed, a push to main reaches the action and reports "publish" -> "publish-script". It neither updates the release PR nor runs pnpm ci:publish.
Recommended fix: Rename the workflow input from publish to publish-script as part of the v2 migration.
Was this helpful? React with 👍 or 👎 to provide feedback.
1cec4fb to
e6d7263
Compare
This PR contains the following updates:
v1.7.0→v2.1.2Release Notes
changesets/action (changesets/action)
v2.1.2Compare Source
Patch Changes
#735
8833883Thanks @bluwy! - Handle error when pushing git tags with the git CLI#724
36f529fThanks @bluwy! - Improve log messages#724
36f529fThanks @bluwy! - Fix root action double error logs#729
ca85897Thanks @bluwy! - Always switch and reset branch when generating version commits, similar to ifpush-with-git-cliis enabledv2.1.1Compare Source
Patch Changes
da1ea29Thanks @KEBABSELLER6! - Fixed typo in renamed inputs from v1 to v2v2.1.0Compare Source
Minor Changes
3b7c71cThanks @bluwy! - Add acwdinput to the root action,/select-mode,/version,/pack, and/publishsub-actions to set the current working directory to execute Changesets in. This input existed in v1 but was incorrectly removed.Patch Changes
6f58ba3Thanks @bluwy! - Updatepr-statusmessage to link to the new faq pagev2.0.0Compare Source
Major Changes
#692
cb3f011Thanks @Andarist! - Release commits and tags are now pushed using the GitHub API by default.Replace the
commit-modeinput with the booleanpush-with-git-cliinput. Setpush-with-git-cli: trueto continue using the Git CLI.Regardless of the push mode, custom GitHub tokens must be passed explicitly through the
github-tokeninput. TheGITHUB_TOKENenvironment variable and credentials configured byactions/checkoutor embedded in remote URLs are not substitutes for this input. When the Git CLI is enabled,github-tokentakes precedence over those repository credentials.#680
ca57073Thanks @bluwy! - Add a newpush-git-tagsoption that complementscreate-github-releasesto control specifically if git tags should be created but not GitHub releases.If
create-github-releaseswas previously set tofalse, which also indirectly disabled git tag creation, git tags will now be created instead by default. If this is not desired, setpush-git-tagstofalseexplicitly.#657
4f718b5Thanks @Andarist! - Removed compatibility support for old Changesets v1.#681
7359107Thanks @bluwy! - Rename the root action inputs and outputs to better match the sub-actions' conventions.Inputs:
version->version-scriptpublish->publish-scriptcommit->commit-messagetitle->pr-titlebranch->pr-base-branchOutputs:
pull-request-number->pr-number#674
164652bThanks @bluwy! - Remove support for passing custom GitHub token through the GITHUB_TOKEN environment variable. It should be passed to thegithub-tokeninput instead.#659
5649ff4Thanks @bluwy! - Removecwdoption forchangesets/action. Use the stepworking-directoryoption instead to change the directory.#673
823cf74Thanks @bluwy! - Update to Changesets v3 packages#695
469993cThanks @bluwy! - Removed.npmrchandling when theNPM_TOKENenvironment variable is set.Authentication should be handled via Trusted Publishing instead. If a token is still needed, use
actions/setup-nodeto set it up instead via theregistry-urloption. Check out the updated action README for more information of setting up npm authentication in GitHub Actions.#668
0eae789Thanks @bluwy! - Rename the input and output names to kebab-case instead of camelCase to match the official GitHub actions patternMinor Changes
#656
a12d90dThanks @bluwy! - Add new/select-mode,/version, and/publishsub-actions to better control version and publish steps#678
f71ae04Thanks @Andarist! - Published packages detection done through stdout parsing was replaced with one based on the shared output file usingCHANGESETS_OUTPUTenvironment variable. When using custom scripts this environment variable should always be passed down to the Changesets CLI invocations.Patch Changes
#699
5b307d3Thanks @Andarist! - Validate that projects use Changesets CLI v3 and direct Changesets CLI v2 users tochangesets/action@v1.#697
84d78c6Thanks @Andarist! - Allow custom publish scripts to complete without a Changesets output file, warning that GitHub releases and git tags cannot be created when that file is missing.#670
5a8b9b7Thanks @Andarist! - Authenticate git CLI pushes with the configured GitHub token using Git extra headers instead of writing to a global.netrcfile.#670
5a8b9b7Thanks @Andarist! - Derive the Git server URL from the GitHub Actions context when configuring git CLI authentication to support GitHub Enterprise Server setups.#688
219ea82Thanks @Andarist! - Remove thesetup-git-userinput. Complete custom Git identities are now preserved automatically, whilegithub-actions[bot]is configured as a fallback before creating local release commits or tags.v1.9.0Compare Source
Minor Changes
#636
b072bccThanks @bluwy! - Add a new@changesets/action/pr-commentsub-action to comment on PRs#625
8795eeeThanks @bluwy! - Add a new@changesets/action/pr-statussub-action to generate the changeset status comment for PRs as an alternative to the Changesets Bot.Patch Changes
#535
34f64f6Thanks @Andarist! - Fixed an issue with GitHub releases not being created for successfully published packages when some packages failed to be published to the registry.#632
1d54b9eThanks @bluwy! - Simplify internal implementation to get changelog entries for a package version#629
e0c90aaThanks @bluwy! - Fix custom version and publish command argument parsing#645
f9585d9Thanks @Andarist! - Improved force-push handling when usingcommitMode: "github-api"so updating an existing branch no longer temporarily resets the target branch to the base commit, avoiding cases where GitHub closes open pull requests during the update. This should remove a possibility of a GitHub state race that caused the force-pushed PRs not being reopened.v1.8.0Compare Source
Minor Changes
f5dbf72Thanks @tom-sherman! - Support draft version PR modes with a newprDraftinput. Usecreateto create new version PRs as drafts, oralwaysto also convert existing version PRs back to draft when updating them.Patch Changes
#502
6002dbdThanks @oshytiko! - Fixed initial.changesetstate being picked up, whencwdparameter is provided#536
81b3f61Thanks @radnan! - Fixed.changesetstate being picked for the version command whencwdparameter is providedConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.