fix(ci): use OIDC id-token for npm publish#235
Conversation
The Blacksmith no-OIDC npm-auth path stopped working — publish 404'd (unauthenticated PUT) on 4.2.3/4.2.4. Adding `id-token: write` switches to npm Trusted Publisher OIDC (no token); verified on a branch dispatch where auth succeeded (got past auth to the version check). Provenance stays disabled (self-hosted Blacksmith runner). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 30 minutes and 42 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The Blacksmith no-OIDC npm-auth path stopped working —
npm publish404'd (unauthenticated PUT) for 4.2.3 and 4.2.4, so neither reached npm. Addingid-token: writeswitches to npm Trusted Publisher OIDC (still token-free). Verified on a branch dispatch: auth succeeded (got past auth to the 'cannot publish over 4.2.3' version check). Provenance stays--provenance=false(self-hosted Blacksmith runner). After merge I'll re-run the publish to ship 4.2.4.🤖 Generated with Claude Code