ci: publish to npm via OIDC trusted publishing - #10
Merged
Conversation
Bump semantic-release to v25, which bundles @semantic-release/npm 13.1.x — the first version to support OIDC trusted publishing. Drop the NPM_TOKEN secret from the Release job; npm auth now flows through the existing id-token: write permission. Add an npm@latest upgrade step because OIDC requires npm >= 11.5.1 and Node 24 ships npm 10.x.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Bump semantic-release to v25, which bundles @semantic-release/npm 13.1.x — the first version to support OIDC trusted publishing.
Drop the NPM_TOKEN secret from the Release job; npm auth now flows through the existing id-token: write permission.
Add an npm@latest upgrade step because OIDC requires npm >= 11.5.1 and Node 24 ships npm 10.x.