fix(ci): create npmrc before changesets to enable OIDC #673
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 #672 attempted to use
skipNpmAuth: truebut this parameter doesn't exist inchangesets/action@v1. The workflow failed with:Root Cause
The
changesets/action@v1creates its own.npmrcfile when it doesn't find one, which expects anNPM_TOKEN. This blocks npm CLI from using OIDC authentication.Solution
Create
~/.npmrcbefore the changesets action runs, configured with the registry and NPM_TOKEN placeholder. This allows npm CLI (11.5.1+) to:.npmrc(so changesets doesn't create one)id-token: writepermission)Changes
How OIDC Works
With trusted publishers configured on npmjs.com and
id-token: writepermission:Verification
All 8 packages already have trusted publishers configured correctly (verified via screenshots).
Testing
Merging this PR will trigger the release workflow, which should successfully publish:
Related