chore: update to yarn 4.11.0 and configure for trusted publisher #34
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
--provenanceflag from publish commands (now handled by .yarnrc.yml)npmAuthTokenfrom .yarnrc.yml (using OIDC instead)npmPublishProvenance: truein .yarnrc.yml for automatic provenance generationContext
Yarn 4.11.0 is required for proper npm trusted publisher support with OIDC authentication. With
npmPublishProvenance: trueset in .yarnrc.yml, provenance is automatically enabled and the--provenanceCLI flag is redundant.The workflow will now authenticate using GitHub's OIDC token (via
id-token: writepermission) and automatically generate provenance attestations through the yarn configuration.🤖 Generated with Claude Code