chore: upgrade to Yarn 4.11.0 for npm trusted publisher support #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.
Summary
npmAuthTokenwithnpmPublishProvenance: truein.yarnrc.yml--provenanceflags from publish commands (now handled automatically by Yarn config)Changes
This implements the same changes as ReforgeHQ/sdk-node#34 for the JavaScript SDK.
Yarn 4.11.0 is required for proper npm trusted publisher support with OIDC authentication. By setting
npmPublishProvenance: truein the Yarn configuration, provenance attestations are now generated automatically without needing the--provenanceCLI flag.The workflow authenticates using GitHub's OIDC token (via the existing
id-token: writepermission) instead of stored authentication tokens, improving security for package publishing.Test plan
🤖 Generated with Claude Code