Repository navigation
ci: publish to npm with trusted publishing instead of a token - #37
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Merged
Contributor
|
🎉 This PR is included in version 0.2.0-rc.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Contributor
|
🎉 This PR is included in version 0.2.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This branch was successfully deployed
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.
The release job now publishes through npm trusted publishing (GitHub OIDC) instead of the
NPM_TOKENsecret. npm is restricting tokens that bypass 2FA for direct publishing.NODE_AUTH_TOKENfrom the semantic-release step.npm@^11.5.1before publishing, the minimum trusted publishing needs.id-token: writewas already granted; provenance stays on.Before the next release runs, register
hyamero/stackmap, workflowci.yml, as a trusted publisher in the package settings on npmjs.com. Once a release has published through OIDC, set publishing access to disallow tokens and deleteNPM_TOKEN.