Repository navigation
fix: restore registry-url for OIDC publish - #5
Merged
Merged
Conversation
Without registry-url npm never attempts the OIDC exchange and fails with ENEEDAUTH. npm's Trusted Publishing setup keeps registry-url and just omits the token; the empty-token concern was a red herring (the earlier 404 was a stale npm 10.x, now fixed by the separate upgrade step).
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.
npm is now 12.0.1 (the upgrade step works), but without registry-url npm has no registry context and skips the OIDC exchange entirely (ENEEDAUTH). npm's Trusted Publishing example keeps registry-url and omits the token, which is what this restores.