Switch to npm publish for OIDC trusted publishing#77
Merged
Conversation
Yarn 4.10.3's OIDC support is not working despite having all required environment variables set correctly. Switch to using npm CLI directly, which has mature OIDC trusted publishing support. Changes: - Remove debug output (no longer needed) - Add npm upgrade step to ensure npm >= 11.5.1 - Switch from "yarn npm publish" to "npm publish" - npm 11.5.1+ supports OIDC authentication automatically This will work with the trusted publishing configuration already set up on npmjs.com for @reforge-com/cli. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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
2 participants
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
Switches from
yarn npm publishtonpm publishfor OIDC trusted publishing support.Problem
Despite Yarn 4.10.3 claiming to support OIDC authentication, it consistently fails with:
Debug output confirmed all required environment variables are set:
CI=trueGITHUB_ACTIONS=trueACTIONS_ID_TOKEN_REQUEST_URLis setACTIONS_ID_TOKEN_REQUEST_TOKENis setYet Yarn's OIDC authentication still fails.
Solution
Use
npm publishdirectly, which has mature and working OIDC trusted publishing support:id-token: writeis setChanges
yarn npm publishtonpm publishTest Plan
After merging:
🤖 Generated with Claude Code