Skip to content

ci: instrument public publish to diagnose OIDC (3 fixes failed) - #8

Merged
vigubikReply merged 1 commit into
mainfrom
dev/diag-public-oidc
Jul 23, 2026
Merged

ci: instrument public publish to diagnose OIDC (3 fixes failed)#8
vigubikReply merged 1 commit into
mainfrom
dev/diag-public-oidc

Conversation

@vigubikReply

Copy link
Copy Markdown
Contributor

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:

  • node & npm versions (need node >= 22.14.0, npm >= 11.5.1)
  • whether ACTIONS_ID_TOKEN_REQUEST_URL/TOKEN env vars are present (i.e. is id-token actually granted to this job)
  • the resolved registry + the .npmrc contents after the strip
  • npm publish --loglevel verbose + dump of npm's debug log on failure

No 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

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>
@vigubikReply
vigubikReply merged commit ad85f68 into main Jul 23, 2026
6 checks passed
@vigubikReply
vigubikReply deleted the dev/diag-public-oidc branch July 23, 2026 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant