Conversation
The repo named Node 24 in several places - the action's production runtime (`action.yml` `using: 'node24'`), the `check-dist` build, and the primary leg of the `test.yml` matrix - but had no `.nvmrc`, so local development relied on whatever Node a contributor happened to have installed. Adding `.nvmrc` gives `nvm use` a single source of truth that matches the version the action actually runs on, without disturbing the intentional `[22, 24]` test matrix or introducing an `engines.node` block the repo deliberately omits.
|
Warning Review limit reached
More reviews will be available in 12 minutes and 32 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 review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
The repo named Node 24 in several places but had no
.nvmrc, so local development relied on whatever Node a contributor happened to have installed. This adds an.nvmrcsonvm useresolves to the version the action actually runs on.Resolved version:
24This isn't arbitrary — it's the version the repo already implies:
action.ymlruntimeusing: 'node24'check-dist.yml(build/sync)24test.ymlmatrix[22, 24](primary leg24)package.jsonengines.node.nvmrc(before)Notes
[22, 24]test matrix is left untouched.engines.nodeblock was introduced — the repo deliberately omits one.setup-nodesteps keep their explicit24, which is deliberately coupled to theaction.ymlnode24runtime pin.🤖 Generated with Claude Code