Skip to content

Added .nvmrc pinning the repo to Node 24#165

Merged
aileen merged 1 commit into
mainfrom
add-nvmrc
Jun 25, 2026
Merged

Added .nvmrc pinning the repo to Node 24#165
aileen merged 1 commit into
mainfrom
add-nvmrc

Conversation

@aileen

@aileen aileen commented Jun 25, 2026

Copy link
Copy Markdown
Member

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 .nvmrc so nvm use resolves to the version the action actually runs on.

Resolved version: 24

This isn't arbitrary — it's the version the repo already implies:

Source Node version
action.yml runtime using: 'node24'
check-dist.yml (build/sync) 24
test.yml matrix [22, 24] (primary leg 24)
package.json engines.node (none, deliberately)
.nvmrc (before) (missing)

Notes

  • The intentional [22, 24] test matrix is left untouched.
  • No engines.node block was introduced — the repo deliberately omits one.
  • CI setup-node steps keep their explicit 24, which is deliberately coupled to the action.yml node24 runtime pin.

🤖 Generated with Claude Code

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.
@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

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 @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 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.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 75eeb0f5-8813-4638-876c-3e71611ef91e

📥 Commits

Reviewing files that changed from the base of the PR and between 7bb8d56 and 82b7e58.

📒 Files selected for processing (1)
  • .nvmrc
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-nvmrc

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

@aileen aileen merged commit 1de12c3 into main Jun 25, 2026
8 checks passed
@aileen aileen deleted the add-nvmrc branch June 25, 2026 10:29
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