ci: bump changesets/action in /

[dependabot]

Bumps changesets/action in / from 1.9.0 to 2.1.2.

Updates changesets/action from 1.9.0 to 2.1.2

Release notes

Sourced from changesets/action's releases.

v2.1.2

Patch Changes

• #735 8833883 Thanks @​bluwy! - Handle error when pushing git tags with the git CLI

• #724 36f529f Thanks @​bluwy! - Improve log messages

• #724 36f529f Thanks @​bluwy! - Fix root action double error logs

• #729 ca85897 Thanks @​bluwy! - Always switch and reset branch when generating version commits, similar to if push-with-git-cli is enabled

v2.1.1

Patch Changes

• #721 da1ea29 Thanks @​KEBABSELLER6! - Fixed typo in renamed inputs from v1 to v2

v2.1.0

Minor Changes

• #718 3b7c71c Thanks @​bluwy! - Add a cwd input to the root action, /select-mode, /version, /pack, and /publish sub-actions to set the current working directory to execute Changesets in. This input existed in v1 but was incorrectly removed.

Patch Changes

• #716 6f58ba3 Thanks @​bluwy! - Update pr-status message to link to the new faq page

v2.0.0

Major Changes

• #692 cb3f011 Thanks @​Andarist! - Release commits and tags are now pushed using the GitHub API by default.

  Replace the commit-mode input with the boolean push-with-git-cli input. Set push-with-git-cli: true to continue using the Git CLI.

  Regardless of the push mode, custom GitHub tokens must be passed explicitly through the github-token input. The GITHUB_TOKEN environment variable and credentials configured by actions/checkout or embedded in remote URLs are not substitutes for this input. When the Git CLI is enabled, github-token takes precedence over those repository credentials.

• #680 ca57073 Thanks @​bluwy! - Add a new push-git-tags option that complements create-github-releases to control specifically if git tags should be created but not GitHub releases.

  If create-github-releases was previously set to false, which also indirectly disabled git tag creation, git tags will now be created instead by default. If this is not desired, set push-git-tags to false explicitly.

• #657 4f718b5 Thanks @​Andarist! - Removed compatibility support for old Changesets v1.

• #681 7359107 Thanks @​bluwy! - Rename the root action inputs and outputs to better match the sub-actions' conventions.

  Inputs:

  • version -> version-script
  • publish -> publish-script
  • commit -> commit-message
  • title -> pr-title
  • branch -> pr-base-branch

... (truncated)

Changelog

Sourced from changesets/action's changelog.

@​changesets/action

2.1.2

Patch Changes

• #735 8833883 Thanks @​bluwy! - Handle error when pushing git tags with the git CLI

• #724 36f529f Thanks @​bluwy! - Improve log messages

• #724 36f529f Thanks @​bluwy! - Fix root action double error logs

• #729 ca85897 Thanks @​bluwy! - Always switch and reset branch when generating version commits, similar to if push-with-git-cli is enabled

2.1.1

Patch Changes

• #721 da1ea29 Thanks @​KEBABSELLER6! - Fixed typo in renamed inputs from v1 to v2

2.1.0

Minor Changes

• #718 3b7c71c Thanks @​bluwy! - Add a cwd input to the root action, /select-mode, /version, /pack, and /publish sub-actions to set the current working directory to execute Changesets in. This input existed in v1 but was incorrectly removed.

Patch Changes

• #716 6f58ba3 Thanks @​bluwy! - Update pr-status message to link to the new faq page

2.0.0

Major Changes

• #692 cb3f011 Thanks @​Andarist! - Release commits and tags are now pushed using the GitHub API by default.

  Replace the commit-mode input with the boolean push-with-git-cli input. Set push-with-git-cli: true to continue using the Git CLI.

  Regardless of the push mode, custom GitHub tokens must be passed explicitly through the github-token input. The GITHUB_TOKEN environment variable and credentials configured by actions/checkout or embedded in remote URLs are not substitutes for this input. When the Git CLI is enabled, github-token takes precedence over those repository credentials.

• #680 ca57073 Thanks @​bluwy! - Add a new push-git-tags option that complements create-github-releases to control specifically if git tags should be created but not GitHub releases.

  If create-github-releases was previously set to false, which also indirectly disabled git tag creation, git tags will now be created instead by default. If this is not desired, set push-git-tags to false explicitly.

• #657 4f718b5 Thanks @​Andarist! - Removed compatibility support for old Changesets v1.

• #681 7359107 Thanks @​bluwy! - Rename the root action inputs and outputs to better match the sub-actions' conventions.

  Inputs:

... (truncated)

Commits

• ae32849 v2.1.2
• 0138f45 Version Packages (#726)
• 8833883 Handle error when pushing git tags with the git CLI (#735)
• e08fde7 Improve log messages (#730)
• 371fd77 Bump human-id in the production-dependencies group across 1 directory (#732)
• 85efcaf Bump actions/checkout in the github-actions group across 1 directory (#734)
• 5bb9d5c Bump the development-dependencies group across 1 directory with 7 updates (#733)
• ca85897 Always prepare branch for version (#729)
• 36f529f Fix root action double error logs (#724)
• d7669c8 Version Packages (#722)
• Additional commits viewable in compare view

[netlify]

✅ Deploy Preview for drivenets-design-system ready!

Name	Link
🔨 Latest commit	dcf5a20
🔍 Latest deploy log	https://app.netlify.com/projects/drivenets-design-system/deploys/6a9fcd7846db3100086f68cc
😎 Deploy Preview	https://deploy-preview-665--drivenets-design-system.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.