Repository navigation
ci(release): let npm publish through Trusted publishing - #38
Merged
Merged
Conversation
Node 24 brings npm 11, which publishes with the workflow's OIDC identity when npm Trusted publishing trusts release.yml, so the expiring NPM_TOKEN is no longer needed. npm falls back to the token until that is set up, and check-secrets now treats the token as optional.
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.
Prepares npm Trusted publishing, so the expiring
NPM_TOKENcan be deleted.release.yml: the npm job uses Node 24 (npm 11). npm 11 publishes with the workflow's OIDC identity when Trusted publishing is set up on npmjs.com, and falls back toNPM_TOKENuntil then. The job already hadid-token: write.check-secrets.yml:NPM_TOKENis now optional.CONTRIBUTING.md: the one-time setup (npm trust github ...) and when to delete the secret.Checked: actionlint passes. Not checked: a real publish through Trusted publishing; that happens on the next release, and the post-release verify-install npm job checks it.