Version Packages (next) - #698
Merged
Merged
Conversation
changesets-org-version-bot
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
July 27, 2026 05:04
bfd1901 to
3c6ec0e
Compare
changesets-org-version-bot
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 1, 2026 09:38
34f2ae0 to
86950a7
Compare
changesets-org-version-bot
Bot
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 12:06
86950a7 to
ab6ac4a
Compare
Andarist
enabled auto-merge
August 3, 2026 12:10
Andarist
approved these changes
Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@changesets/action@2.0.0-next.4
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.#695
469993cThanks @bluwy! - Removed.npmrchandling when theNPM_TOKENenvironment variable is set.Authentication should be handled via Trusted Publishing instead. If a token is still needed, use
actions/setup-nodeto set it up instead via theregistry-urloption. Check out the updated action README for more information of setting up npm authentication in GitHub Actions.Patch Changes
#699
5b307d3Thanks @Andarist! - Validate that projects use Changesets CLI v3 and direct Changesets CLI v2 users tochangesets/action@v1.#697
84d78c6Thanks @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.#705
77be81bThanks @Andarist! - Fixed a regression making it impossible to sync new versions of versioning pull requests with base branch updates when using GitHub API pushes.#688
219ea82Thanks @Andarist! - Remove thesetup-git-userinput. Complete custom Git identities are now preserved automatically, whilegithub-actions[bot]is configured as a fallback before creating local release commits or tags.