chore(release): dump npm debug log on publish failure#239
Closed
cipolleschi wants to merge 1 commit into
Closed
Conversation
Surfaces npm's full-detail debug log (including the OIDC trusted-publishing decision) so we can see why npm falls back to ENEEDAUTH instead of using OIDC.
Contributor
Author
|
Superseded by #240 — the debug log isn't needed; root cause identified as setup-node@v4 predating OIDC support. |
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.
Second diagnostic. The OIDC id-token IS available (previous diagnostic confirmed), npm is 11.16.0, and no token is configured — yet
npm publishreturnsENEEDAUTHwith no OIDC-related output on the console.npm always writes a full-detail debug log to
~/.npm/_logs/*-debug-0.logregardless of console loglevel. This adds anif: failure()step that prints it, so we can see whether npm attempted the OIDC token exchange and what the registry replied (e.g. no trusted publisher configured / claim mismatch).Revert once the release is green.