Skip to content

fix(node-ci): set up Node for bun projects too - #40

Merged
WomB0ComB0 merged 1 commit into
mainfrom
fix/node-ci-setup-node-for-bun
Jul 30, 2026
Merged

fix(node-ci): set up Node for bun projects too#40
WomB0ComB0 merged 1 commit into
mainfrom
fix/node-ci-setup-node-for-bun

Conversation

@WomB0ComB0

Copy link
Copy Markdown
Member

setup-node was gated if: package-manager != 'bun'. But native/postinstall deps (sharp, cypress) spawn node during bun install. On GitHub-hosted runners system Node is modern so it worked by accident; on a self-hosted runner with old system Node, bun install crashes in cypress's postinstall (parsed under Node 12). Runs setup-node for every PM now — bun also gets a pinned modern Node on PATH, no npm cache for bun, non-bun paths unchanged.

setup-node was gated `if: package-manager != 'bun'`, on the assumption bun
projects don't need Node. But native and postinstall deps (sharp, cypress, …)
spawn `node` during `bun install`. On GitHub-hosted runners the system Node is
modern so it worked by accident; on a self-hosted runner with an old system
Node, `bun install` crashes in the postinstall (e.g. cypress's cli parsed
under Node 12 → "Unexpected token =").

Runs setup-node for every package manager now. bun still gets setup-bun; it
just also gets a pinned modern Node on PATH. No npm/yarn/pnpm cache is enabled
for bun (it manages its own store), so nothing else changes for bun callers,
and non-bun paths are byte-identical.
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 26 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d4d6650f-eb0a-4641-a0f9-0457240ab874

📥 Commits

Reviewing files that changed from the base of the PR and between 4a158bc and 6833969.

📒 Files selected for processing (1)
  • .github/workflows/node-ci.yml

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.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@WomB0ComB0
WomB0ComB0 merged commit a8c134f into main Jul 30, 2026
8 checks passed
@WomB0ComB0
WomB0ComB0 deleted the fix/node-ci-setup-node-for-bun branch July 30, 2026 05:11
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