Repository navigation
Make npm trusted-publishing failures diagnosable - #4
Merged
Merged
Conversation
Log npm/node versions and publish with --loglevel verbose so the OIDC token exchange is visible, and clear setup-node's placeholder NODE_AUTH_TOKEN so a failed exchange is reported as an auth error rather than a misleading E404.
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.
The npm trusted publish for
js-v1.0.5fails withE404, and there's no provenance notice, so the OIDC exchange isn't completing. The logs don't say why.This change:
--loglevel verbose, which logs the OIDC exchangeNODE_AUTH_TOKEN(XXXXX-…), so a failed exchange doesn't fall back to a bogus tokenAfter merging,
js-v1.0.5is re-pointed to the merge commit. It never produced a release.