fix(release): use setup-node v6 with registry-url for OIDC npm auth#390
Merged
fix(release): use setup-node v6 with registry-url for OIDC npm auth#390
Conversation
Matches the pattern from ExpediaGroup/graphql-component#115: - Upgrade actions/setup-node from v4 to v6 - Add registry-url: https://registry.npmjs.org/ - setup-node v6 + registry-url + id-token:write handles OIDC auth Revert .releaserc.json to use @semantic-release/npm since OIDC auth is now properly configured by setup-node.
mohnoor94
force-pushed
the
fix-release-npm-publish
branch
from
f8d07a2 to
9d3fce0
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
actions/setup-nodefrom v4 to v6registry-url: https://registry.npmjs.org/to setup-node config.releaserc.jsonto use@semantic-release/npm(plain, no provenance hack)Why this works
Matches the pattern used by other EG OSS packages (e.g. graphql-component#115):
setup-node@v6+registry-url+id-token: write= OIDC-based npm authPrevious attempts
All prior PRs (#385-389) failed because we were missing the
registry-urlconfig onsetup-node, which is what actually enables OIDC auth for npm.🤖 Generated with Claude Code