chore: upgrade GitHub Actions to Node 24 runtimes#20
Conversation
|
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. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Summary
actions/setup-nodefromv4tov6actions/checkoutfromv4tov6anywhere these workflows use Node-based GitHub actionsWhy
actions/setup-node@v4andactions/checkout@v4still run on the deprecated Node 20 action runtimeactions/setup-node v6.3.0andactions/checkout v6.0.2, both on the Node 24 lineValidation
YAML.load_filenpx prettier --check .github/workflows/*.ymlnpm test