ci: fix npm token secret name#220
Conversation
The npm-publish step referenced secrets.NPM_TOKEN, but the actual secret is NPM_PUBLISH_PRIVATE_TOKEN. Without this, the step errored with a 404 from npm (token authenticated but had no publish rights for the @rainlanguage scope). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Warning Review limit reached
Your plan currently allows 1 review/hour. Refill in 37 minutes and 56 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE 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 |
|
Superseded by #221 which includes the NPM_TOKEN -> NPM_PUBLISH_PRIVATE_TOKEN rename plus rainix bump and publish reorder. |
1 participant
The npm-publish step referenced
secrets.NPM_TOKENbut the actual configured secret isNPM_PUBLISH_PRIVATE_TOKEN. Without this, the workflow failed at the NPM publish step with 404, and crates.io publish never ran because it's gated after.