ci: restore registry-url for OIDC (fixes ENEEDAUTH) - #6
Merged
Conversation
Removing registry-url left npm with no registry configured, so it couldn't do the OIDC exchange (ENEEDAUTH). The npm docs keep registry-url: npm CLI >= 11.5.1 detects OIDC and authenticates with it before falling back to the setup-node placeholder token. Restore registry-url; keep npm publish.
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.
Follow-up to #5 — that run failed with
ENEEDAUTH("need auth… npm login").Removing `registry-url` went too far: npm had no registry configured, so it couldn't perform the OIDC token exchange. The npm docs keep `registry-url` — npm CLI (≥ 11.5.1) detects the OIDC environment and authenticates with it before falling back to the setup-node placeholder token. (That placeholder was only a problem for `pnpm publish`, which is why we publish with `npm publish`.)
Fix: restore `registry-url: 'https://registry.npmjs.org'\`; keep
npm install -g npm@latest+npm publish. This matches the official npm trusted-publishing workflow.Merging triggers the workflow; should publish via OIDC.