ci: fix build by dropping Node.js version matrix#450
ci: fix build by dropping Node.js version matrix#450PascalRepond merged 1 commit intorero:stagingfrom
Conversation
Remove the Node.js matrix strategy (18.19.x, 20.11.x, 22.x) and fix the CI to Node.js 22 only. Node 18 (end-of-life since April 2025) ships with npm 9.x which has a known bug with optional native dependencies (npm/cli#4828). This caused @tailwindcss/oxide to fail loading its native binding on CI. Testing multiple Node versions brings no value for a frontend Angular library: the compiled output targets browsers, not Node.js. The publishing workflow already uses Node 22, so the build workflow now mirrors it. Co-Authored-by: Pascal Repond <pascal.repond@rero.ch>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
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 |
Remove the Node.js matrix strategy (18.19.x, 20.11.x, 22.x) and fix the CI to Node.js 22 only.
Node 18 (end-of-life since April 2025) ships with npm 9.x which has a known bug with optional native dependencies (npm/cli#4828). This caused @tailwindcss/oxide to fail loading its native binding on CI.
Testing multiple Node versions brings no value for a frontend Angular library: the compiled output targets browsers, not Node.js. The publishing workflow already uses Node 22, so the build workflow now mirrors it.