v2.0.0-next.3

Major Changes

• #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.

• #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.

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

• #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

• #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.

v2.0.0-next.2

Patch Changes

• #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.

v2.0.0-next.1

Patch Changes

• #663 ccb3811 Thanks @Andarist! - Fix the computed publish plan path passed internally to changeset pack by the /pack subaction.

• #662 5c88881 Thanks @Andarist! - Fixed usage of --from-publish-plan flag used by the /pack subaction

• #666 dc29b73 Thanks @Andarist! - Fix the /version subaction to not crash on missing pr-base-branch input. This input is meant to be optional.

v2.0.0-next.0

Major Changes

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

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

Minor Changes

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

v1.9.0

Minor Changes

• #636 b072bcc Thanks @bluwy! - Add a new @changesets/action/pr-comment sub-action to comment on PRs

• #625 8795eee Thanks @bluwy! - Add a new @changesets/action/pr-status sub-action to generate the changeset status comment for PRs as an alternative to the Changesets Bot.

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

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

• #502 6002dbd Thanks @oshytiko! - Fixed initial .changeset state being picked up, when cwd parameter is provided

• #536 81b3f61 Thanks @radnan! - Fixed .changeset state being picked for the version command when cwd parameter is provided

v1.7.0

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

Minor Changes

• #558 342005d Thanks @harsha-venugopal-ledn! - Upgrade from Node.js 20 to Node.js 24 LTS

v1.5.3

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

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.