fix(ci): configure registry-url and update npm for OIDC publishing #2
Conversation
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
The OIDC token exchange succeeded during verification but failed during publish with ENEEDAUTH. This fix: - Adds registry-url to setup-node action to properly configure OIDC context - Updates npm to latest version to ensure OIDC trusted publishing support See: npm/cli#8730
github-actions bot
added a commit
that referenced
this pull request
Jan 14, 2026
## [2.0.2](v2.0.1...v2.0.2) (2026-01-14) ### Bug Fixes * **ci:** configure registry-url and update npm for OIDC publishing ([#2](#2)) ([56e1af3](56e1af3))
Contributor
|
🎉 This PR is included in version 2.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Summary
Fixes the
ENEEDAUTHerror that occurred during npm publish despite successful OIDC token exchange. The previous PR #1 enabled trusted publishing, but the workflow was missing configuration needed to properly pass OIDC credentials to the publish step.Changes
registry-url: 'https://registry.npmjs.org'tosetup-nodeaction to properly configure the npm registry for OIDC authenticationRoot Cause
The OIDC token exchange succeeded during verification but the publish step failed because:
setup-nodeaction wasn't configured with the registry URL, so the OIDC context wasn't properly establishedReferences
Test Plan
main