chore(deps): bump changesets/action from 1.9.0 to 2.1.2
Bumps changesets/action from 1.9.0 to 2.1.2.
Release notes
Sourced from changesets/action's releases.
v2.1.2
Patch Changes
#735
8833883Thanks@bluwy! - Handle error when pushing git tags with the git CLI#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.1
Patch Changes
- #721
da1ea29Thanks@KEBABSELLER6! - Fixed typo in renamed inputs from v1 to v2v2.1.0
Minor Changes
- #718
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
v2.0.0
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-branch
... (truncated)
Changelog
Sourced from changesets/action's changelog.
@changesets/action2.1.2
Patch Changes
#735
8833883Thanks@bluwy! - Handle error when pushing git tags with the git CLI#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 enabled2.1.1
Patch Changes
- #721
da1ea29Thanks@KEBABSELLER6! - Fixed typo in renamed inputs from v1 to v22.1.0
Minor Changes
- #718
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
2.0.0
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:
... (truncated)
Commits
ae32849v2.1.20138f45Version Packages (#726)8833883Handle error when pushing git tags with the git CLI (#735)e08fde7Improve log messages (#730)371fd77Bump human-id in the production-dependencies group across 1 directory (#732)85efcafBump actions/checkout in the github-actions group across 1 directory (#734)5bb9d5cBump the development-dependencies group across 1 directory with 7 updates (#733)ca85897Always prepare branch for version (#729)36f529fFix root action double error logs (#724)d7669c8Version Packages (#722)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Summary by cubic
Bumps changesets/action from 1.9.0 to 2.1.2. This is a major version bump with breaking input renames and token handling changes that require updating version-or-publish.yml.
Migration
- Rename
versiontoversion-scriptandpublishtopublish-scriptin the workflow'swithblock. - Provide
github-tokenexplicitly; v2 no longer reads it fromGITHUB_TOKENor checkout credentials. - Release commits and tags now push via the GitHub API by default; set
push-with-git-cli: trueto keep the old Git CLI behavior.