Merged
Conversation
github-actions
bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
680022d to
529b7db
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
529b7db to
95fde0a
Compare
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.
Releases
@changesets/action@1.7.0
Minor Changes
935fe87Thanks @Andarist! - Automatically use the GitHub-provided token to allow most users to avoid explicitGITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}configuration.Patch Changes
#545
54220ddThanks @ryanbas21! - The.npmrcgeneration now intelligently handles both traditional NPM token authentication and trusted publishing scenarios by only appending the auth token whenNPM_TOKENis defined. This prevents 'undefined' from being written to the registry configuration when using OIDC tokens from GitHub Actions trusted publishing.#563
6af4a7eThanks @Andarist! - Don't error on already committed symlinks and executables that stay untouched