[ef-42] feat: re-add --provenance to npm publish for public repo#42
Conversation
The --provenance flag and id-token permission were removed in 407611f because npm provenance requires a public repository. Now that the repo is going public, re-enable provenance attestation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe GitHub Actions publish workflow is updated to enable npm package provenance. The job permissions are expanded to include Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
Summary
--provenanceflag tonpm publishin the publish workflowid-token: writepermission required for npm provenance attestationTest plan
npm publishtriggered by a GitHub release🤖 Generated with Claude Code
Summary by CodeRabbit