π§ [PB-1278] Fix OIDC authentication - remove NODE_AUTH_TOKEN #22
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
This PR fixes npm OIDC trusted publishing authentication by removing the
NODE_AUTH_TOKENenvironment variable from the publish step.Changes
NODE_AUTH_TOKENenv block from deploy.ymlRoot Cause
Research revealed that setting
NODE_AUTH_TOKENto any value (even an empty string'') prevents OIDC authentication from working. The variable must be completely absent for npm to use OIDC trusted publishing.Why This Should Work Now
NODE_AUTH_TOKEN: ''which actively blocked OIDCConfiguration Verified
id-token: writepermission setenvironment: npm-productionmatches npm configregistry-urlconfigured in setup-nodeTesting
Once merged, the workflow will automatically:
References
Note: If this fails again, we'll fall back to traditional npm token authentication.