Skip to content

chore(deps): update changesets/action action to v2 - #158

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/changesets-action-2.x
Open

chore(deps): update changesets/action action to v2#158
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/changesets-action-2.x

Conversation

@renovate

@renovate renovate Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
changesets/action action major v1.4.5v2.1.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

changesets/action (changesets/action)

v2.1.1

Compare Source

v2.1.0

Compare Source

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

v2.0.0

Compare Source

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

    Outputs:

    • pull-request-number -> pr-number
  • #​674 164652b Thanks @​bluwy! - Remove support for passing custom GitHub token through the GITHUB_TOKEN environment variable. It should be passed to the github-token input instead.

  • #​659 5649ff4 Thanks @​bluwy! - Remove cwd option for changesets/action. Use the step working-directory option instead to change the directory.

  • #​673 823cf74 Thanks @​bluwy! - Update to Changesets v3 packages

  • #​695 469993c Thanks @​bluwy! - Removed .npmrc handling when the NPM_TOKEN environment variable is set.

    Authentication should be handled via Trusted Publishing instead. If a token is still needed, use actions/setup-node to set it up instead via the registry-url option. Check out the updated action README for more information of setting up npm authentication in GitHub Actions.

  • #​668 0eae789 Thanks @​bluwy! - Rename the input and output names to kebab-case instead of camelCase to match the official GitHub actions pattern

Minor Changes
  • #​656 a12d90d Thanks @​bluwy! - Add new /select-mode, /version, and /publish sub-actions to better control version and publish steps

  • #​678 f71ae04 Thanks @​Andarist! - Published packages detection done through stdout parsing was replaced with one based on the shared output file using CHANGESETS_OUTPUT environment variable. When using custom scripts this environment variable should always be passed down to the Changesets CLI invocations.

Patch Changes
  • #​699 5b307d3 Thanks @​Andarist! - Validate that projects use Changesets CLI v3 and direct Changesets CLI v2 users to changesets/action@v1.

  • #​697 84d78c6 Thanks @​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 5a8b9b7 Thanks @​Andarist! - Authenticate git CLI pushes with the configured GitHub token using Git extra headers instead of writing to a global .netrc file.

  • #​670 5a8b9b7 Thanks @​Andarist! - Derive the Git server URL from the GitHub Actions context when configuring git CLI authentication to support GitHub Enterprise Server setups.

  • #​688 219ea82 Thanks @​Andarist! - Remove the setup-git-user input. Complete custom Git identities are now preserved automatically, while github-actions[bot] is configured as a fallback before creating local release commits or tags.

v1.9.0

Compare Source

Minor Changes
Patch Changes
  • #​535 34f64f6 Thanks @​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 1d54b9e Thanks @​bluwy! - Simplify internal implementation to get changelog entries for a package version

  • #​629 e0c90aa Thanks @​bluwy! - Fix custom version and publish command argument parsing

  • #​645 f9585d9 Thanks @​Andarist! - Improved force-push handling when using commitMode: "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.0

Compare Source

Minor Changes
  • #​258 f5dbf72 Thanks @​tom-sherman! - Support draft version PR modes with a new prDraft input. Use create to create new version PRs as drafts, or always to also convert existing version PRs back to draft when updating them.
Patch Changes

v1.7.0

Compare Source

Minor Changes
  • #​564 935fe87 Thanks @​Andarist! - Automatically use the GitHub-provided token to allow most users to avoid explicit GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} configuration.
Patch Changes
  • #​545 54220dd Thanks @​ryanbas21! - The .npmrc generation now intelligently handles both traditional NPM token authentication and trusted publishing scenarios by only appending the auth token when NPM_TOKEN is defined. This prevents 'undefined' from being written to the registry configuration when using OIDC tokens from GitHub Actions trusted publishing.

  • #​563 6af4a7e Thanks @​Andarist! - Don't error on already committed symlinks and executables that stay untouched

v1.6.0

Compare Source

Minor Changes

v1.5.3

Compare Source

Patch Changes
  • #​477 9d933dc Thanks @​Andarist! - Updated @actions/* and @octokit/* dependencies.

  • #​479 cf373e4 Thanks @​Andarist! - Switched to esbuild for bundling the dist file. This led to 45% file size reduction.

  • #​488 022692b Thanks @​s0! - Fix PRs sometimes not getting reopened with commitMode: github-api

    There was a race-condition that means sometimes existing PRs would not be found,
    and new PRs would be opened. This has now been fixed by fetching existing PRs
    before making any changes.

  • #​486 7ed1955 Thanks @​s0! - Fixed situations in which cwd was specified as a relative path and used with (default) commitMode: git-cli

  • #​461 e9c36b6 Thanks @​nayounsang! - Avoid hitting a deprecation warning when encountering errors from @octokit/request-error

v1.5.2

Compare Source

Patch Changes
  • #​473 3c24abe Thanks @​s0! - Make git add work consistently with subdirectories

    Ensure that when running the action from a subdirectory of a repository,
    only the files from that directory are added, regardless of commitMode.

v1.5.1

Compare Source

Patch Changes
  • #​471 15ab130 Thanks @​h3rmanj! - Bump @changesets/ghcommit to v1.4.0, which fixes an issue running this action in monorepos with commitMode: github-api

  • #​467 6e57550 Thanks @​Vx-V! - Avoid searching for an existing pull request early.

v1.5.0

Compare Source

Minor Changes
  • #​391 207dc3d Thanks @​s0! - Introduce a new input commitMode that allows using the GitHub API for pushing tags and commits instead of the Git CLI.

    When used with "github-api" value all tags and commits will be attributed to the user whose GITHUB_TOKEN is used, and also signed using GitHub's internal GPG key.

v1.4.10

Compare Source

Patch Changes
  • #​448 8b16070 Thanks @​bluwy! - Use full git email (41898282+github-actions[bot]@users.noreply.github.com) for github-actions bot when making commits

v1.4.9

Compare Source

Patch Changes

v1.4.8

Compare Source

Patch Changes

v1.4.7

Compare Source

Patch Changes

v1.4.6

Compare Source

Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Aug 16, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3b60a07

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/changesets-action-2.x branch from 4e123db to 3b60a07 Compare August 22, 2026 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants