Skip to content

chore: bump Node.js from 20 to 24 in workflows and esbuild target#595

Merged
stehessel merged 1 commit into
mainfrom
chore/bump-node-24
Jun 30, 2026
Merged

chore: bump Node.js from 20 to 24 in workflows and esbuild target#595
stehessel merged 1 commit into
mainfrom
chore/bump-node-24

Conversation

@stehessel

@stehessel stehessel commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Description

Bump to node 24. Closes #588

Add engines field to package.json as the single source of truth for the Node version and reference it via node-version-file in workflows. Also unpin setup-node from v6.4.0 to v6.

@stehessel stehessel requested a review from a team as a code owner June 23, 2026 11:19
@coderabbitai

coderabbitai Bot commented Jun 23, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@stehessel, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 12 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.

How can I continue?

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

How do review 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 refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 6cf6c420-4e5e-4d77-821e-308c08a7d626

📥 Commits

Reviewing files that changed from the base of the PR and between c24f2e0 and 56579d1.

📒 Files selected for processing (4)
  • .github/workflows/lint.yml
  • .github/workflows/package.yml
  • action.yml
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-node-24

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.

@stehessel stehessel force-pushed the chore/prettier-formatting branch from cde876c to a336cf8 Compare June 30, 2026 12:47
Base automatically changed from chore/prettier-formatting to main June 30, 2026 13:29
@stehessel stehessel force-pushed the chore/bump-node-24 branch from 891430e to 96cf6bc Compare June 30, 2026 13:30
Add engines field to package.json as the single source of truth for
the Node version and reference it via node-version-file in workflows.
Also unpin setup-node from v6.4.0 to v6.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@stehessel stehessel force-pushed the chore/bump-node-24 branch from 96cf6bc to 56579d1 Compare June 30, 2026 13:34
@stehessel stehessel enabled auto-merge (squash) June 30, 2026 13:34
@stehessel stehessel merged commit d8ee9cf into main Jun 30, 2026
4 checks passed
@stehessel stehessel deleted the chore/bump-node-24 branch June 30, 2026 13:37
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.

bump to Node.js 24

2 participants