Repository navigation
ci: publish to npm via trusted publishing (OIDC) - #5
Merged
Merged
Conversation
Replace the NPM_TOKEN secret with GitHub OIDC trusted publishing.
Merged
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.
Switches the release workflow from a long-lived
NPM_TOKENsecret to npm trusted publishing via GitHub OIDC.publishjob getsid-token: write(and drops tocontents: read)NODE_AUTH_TOKENremoved from the publish stepThe trusted publisher (
apinator-io/ this repo /release.yml) is already configured on npmjs.com.After the first release publishes successfully this way: set the package to "Require 2FA and disallow tokens" on npmjs.com, revoke the old token, and delete the
NPM_TOKENrepo secret.