ci: add temporary npm/OIDC publish diagnostics#234
Merged
Conversation
geist@1.7.2 fails to publish with ENEEDAUTH despite OIDC trusted publishing working two weeks ago with an unchanged workflow. Print node/npm/pnpm versions (and which binary), the registry, and whether the OIDC token endpoint is exposed to the job, to confirm or rule out npm not using the OIDC-capable binary at publish time. Temporary; remove once the publish is fixed.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Temporary diagnostic to debug the
geist@1.7.2publish failing withENEEDAUTH(OIDC trusted publishing worked 2 weeks ago with an unchanged workflow).Adds a step before
changeset publishthat prints node/npm/pnpm versions + which binary, the registry, and whether the OIDC token endpoint is exposed to the job.Note:
release-npmonly runs onmain, so this needs to be merged to produce output — the next push tomainre-attempts the (still-unpublished) 1.7.2 publish, hits the diagnostic, then fails again as expected, giving us the data. Remove once the publish is fixed.