ci: instrument public publish to diagnose OIDC (3 fixes failed) - #8
Merged
Conversation
Print node/npm versions, id-token env presence, registry, and .npmrc; publish at verbose loglevel and dump npm debug log on failure. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Three fixes haven't made npm attempt the OIDC exchange (still ENEEDAUTH after stripping the empty _authToken). Rather than guess again, this adds diagnostics to capture the ground truth in one run:
ACTIONS_ID_TOKEN_REQUEST_URL/TOKENenv vars are present (i.e. is id-token actually granted to this job).npmrccontents after the stripnpm publish --loglevel verbose+ dump of npm's debug log on failureNo behavior change to the publish itself. If OIDC happens to work, it publishes 0.3.0 (goal); if not, we get the exact reason.
Ref: REPLY-51236