fix(ci): configure changesets to skip npm auth for OIDC #672
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.
Problem
PR #671 enabled OIDC trusted publishing and all 8 packages have been configured on npmjs.com, but the publish still failed with:
Root Cause
The
changesets/action@v1was creating an.npmrcfile expecting the (now removed)NPM_TOKENenvironment variable. This prevented npm CLI from auto-detecting the OIDC environment and using trusted publishers.From the logs:
Solution
Added
skipNpmAuth: trueto the changesets action configuration. This prevents the action from creating token-based authentication, allowing npm CLI (11.5.1+) to automatically detect and use OIDC authentication.How OIDC Works
With
id-token: writepermission and trusted publishers configured:No
NPM_TOKENsecret needed!Verification
All 8 packages have trusted publishers configured:
Testing
This can be verified by:
Related