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

  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.