ci: swap buildjet/setup-node for actions/setup-node v6.4.0#3497
ci: swap buildjet/setup-node for actions/setup-node v6.4.0#3497
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (10)
📜 Recent review details⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (22)
🧰 Additional context used🧠 Learnings (3)📓 Common learnings📚 Learning: 2026-01-15T10:48:02.687ZApplied to files:
📚 Learning: 2026-04-15T15:39:06.868ZApplied to files:
🔇 Additional comments (18)
WalkthroughThis pull request updates GitHub Actions workflows across ten files by replacing the Node.js setup action from Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. Review rate limit: 6/8 reviews remaining, refill in 10 minutes and 1 second.Comment |
|
ready |
Last action still firing the Node 20 deprecation warning after #3494.
buildjet/setup-node@v4.0.4(the latest tag) declaresruns: using: 'node20'and the repo hasn't shipped a node24 update.Workflows here run on
ubuntu-latest(not buildjet runners), so the buildjet fork wasn't giving us anything we don't get fromactions/setup-nodedirectly. Swapping toactions/setup-node@v6.4.0(node24 runtime) silences the warning.