Skip to content

ci(publish): install node 22 in the CircleCI publish job - #74

Merged
sedghi merged 1 commit into
mainfrom
fix/circleci-publish-node
Jul 9, 2026
Merged

ci(publish): install node 22 in the CircleCI publish job#74
sedghi merged 1 commit into
mainfrom
fix/circleci-publish-node

Conversation

@sedghi

@sedghi sedghi commented Jul 9, 2026

Copy link
Copy Markdown
Member

Problem

The npm publish on main is failing at yarn install:

error vite@7.3.6: The engine "node" is incompatible with this module. Expected version "^20.19.0 || >=22.12.0". Got "20.18.0"
error Found incompatible module.

Cause

The CircleCI NPM_PUBLISH job runs on the emscripten/emsdk:3.1.74 image, which bundles node 20.18.0. vite@7 (pulled in transitively by vitest 3) requires ^20.19.0 || >=22.12.0, so yarn's engine check aborts the install and the publish never runs. The GitHub Actions build job already avoids this by layering actions/setup-node@v4 (node 22) on top of the emsdk container; the CircleCI publish job never got the same treatment.

Fix

Install node 22 in the install-build-tools command and put it first on PATH (via $BASH_ENV) before yarn install, mirroring the GitHub build job. emcc keeps using its own configured node, so the wasm build in build:publish is unaffected.

Scope: .circleci/config.yml only.

The emsdk 3.1.74 image ships node 20.18.0, but vite 7 (transitive via
vitest 3) requires ^20.19.0 || >=22.12.0, so 'yarn install' in the
NPM_PUBLISH job fails its engine check and the publish never runs. Install
node 22 and put it first on PATH before yarn install, mirroring the
setup-node@v4 step the GitHub Actions build job already uses. emcc keeps
its own configured node, so the wasm build is unaffected.
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 6 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: 31b1ae3b-9d43-45b2-95d9-440f76fe5ea5

📥 Commits

Reviewing files that changed from the base of the PR and between fcfb2c2 and d45f8a5.

📒 Files selected for processing (1)
  • .circleci/config.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/circleci-publish-node

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.

@sedghi
sedghi merged commit a88a461 into main Jul 9, 2026
8 checks passed
@sedghi
sedghi deleted the fix/circleci-publish-node branch July 9, 2026 14:18
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