Repository navigation
Conversation
The publish workflow pushes each release straight to the registry with `npm publish`, so a version goes public with no maintainer proof-of-presence (2FA) at any point. Use `npm stage publish`, the flow npm recommends for automated pipelines: the workflow uploads the package in a staged state and a maintainer approves it with 2FA (`npm stage approve`) before it becomes public. Provenance and the OIDC trusted-publishing setup are kept as is.
ci: stage npm releases instead of publishing them directly
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.
What does this PR do?
CI: Use
npm stage publish, the flow npm recommends for automated pipelines.