Document npm trusted publishing prerequisites#26
Open
plutoless wants to merge 1 commit into
Open
Conversation
plutoless
force-pushed
the
fix/npm-publish-bootstrap-auth
branch
from
f5fb276 to
227aaa0
Compare
plutoless
changed the title
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
1 participant
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.
Summary
Root cause
The release workflow already uses OIDC trusted publishing, but npm returns ENEEDAUTH when the package's trusted publisher configuration does not match the GitHub workflow or has not been configured. npm's docs also state package trust configuration requires an existing registry package.
Tests