[BUGFIX] Fix npm auth issues after OIDC disable #21
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.
Description
Fixes npm authentication failures in the release workflow after OIDC was temporarily disabled. The release was failing with 401 Unauthorized errors during the
verifyConditionsstep.Changes Made
provenance: truefrompublishConfiginpackage.json- provenance attestations require OIDC authentication (id-token: writepermission)NODE_AUTH_TOKENenvironment variable to the release workflow - thesetup-nodeaction creates an.npmrcfile that expects this variable for npm CLI authenticationDefinition of Done
Additional Notes
Once OIDC is re-enabled in the future,
provenance: truecan be added back topublishConfigto enable npm provenance attestations.