Skip to content

fix(ci): restore NODE_AUTH_TOKEN on npm publish step#234

Closed
jbiskur wants to merge 1 commit into
mainfrom
fix/ci-npm-publish-auth
Closed

fix(ci): restore NODE_AUTH_TOKEN on npm publish step#234
jbiskur wants to merge 1 commit into
mainfrom
fix/ci-npm-publish-auth

Conversation

@jbiskur

@jbiskur jbiskur commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

The Blacksmith migration (13f567b) dropped NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} from the Publish-to-NPM step, so npm publish ran unauthenticated and 404'd on every release since — 4.2.3 and 4.2.4 never reached npm. Restoring the env so the publish authenticates again.

🤖 Generated with Claude Code

The Blacksmith migration (13f567b) dropped the NODE_AUTH_TOKEN env from the
Publish to NPM step, so npm publish ran unauthenticated and 404'd on every
release since (4.2.3, 4.2.4 never reached npm). Restore the token env.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@jbiskur, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 38 minutes and 23 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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ae60dace-a70f-4f52-bcfa-bfb46c9859cd

📥 Commits

Reviewing files that changed from the base of the PR and between a5266a4 and 1d734a0.

📒 Files selected for processing (1)
  • .github/workflows/build.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/ci-npm-publish-auth

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jbiskur jbiskur closed this Jun 23, 2026
@jbiskur jbiskur deleted the fix/ci-npm-publish-auth branch June 23, 2026 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant