Repository navigation
ci: let the first npm release publish with an NPM_TOKEN secret - #3
Merged
Merged
Conversation
npm only lets a trusted publisher be attached to an existing package, so the first release needs a token. When the NPM_TOKEN secret is set the release publishes with it; otherwise it uses Trusted Publishing as before.
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.
npm only lets a trusted publisher be attached to a package that already exists, and a manual first publish from the CLI needs an interactive 2FA prompt. So the first release publishes from CI with an
NPM_TOKENsecret (a 7-day granular token limited to the@flamaiscope).NPM_TOKENis set, the release job publishes with it.After
@flamai/finesse@0.1.1is published: add the trusted publisher on npmjs.com, delete theNPM_TOKENsecret and revoke the token.