ci(publish): install node 22 in the CircleCI publish job - #74
Conversation
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.
|
Warning Review limit reached
Next review available in: 6 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 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Problem
The npm publish on
mainis failing atyarn install:Cause
The CircleCI
NPM_PUBLISHjob runs on theemscripten/emsdk:3.1.74image, 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 layeringactions/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-toolscommand and put it first onPATH(via$BASH_ENV) beforeyarn install, mirroring the GitHub build job.emcckeeps using its own configured node, so the wasm build inbuild:publishis unaffected.Scope:
.circleci/config.ymlonly.