build!: bump dependencies, require node 24#58
Conversation
Signed-off-by: Guillaume Bonnet <mrsquaare@mrsquaare.fr>
Signed-off-by: Guillaume Bonnet <mrsquaare@mrsquaare.fr>
📝 WalkthroughWalkthroughThis PR updates the project to support Node.js 24, replacing Node.js 20 across GitHub Actions configuration, documentation, and package dependencies. Updates include action runtime specifications, GitHub Actions setup configuration, README documentation, and package.json engine requirements and tool versions. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 Tip CodeRabbit can enforce grammar and style rules using `languagetool`.Configure the |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@action.yml`:
- Around line 29-30: The action currently sets the runner runtime to node24 via
the "runs: using: \"node24\"" entry which will break older self-hosted runners;
revert the runtime to the previous LTS (e.g., "node20") in action.yml for the
existing major (v3) release and instead introduce node24 in a new major release
(v4). Update the new major's action.yml to use "node24", add clear migration
notes in the release/changelog and README explaining the required self-hosted
runner minimum (v2.327.1+) and migration steps, and keep the existing
tag/version for consumers who must remain on node20 to avoid breaking them.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: cd7fbf42-b262-4d3b-81d7-294df9409b6e
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (4)
.github/actions/setup-env/action.ymlREADME.mdaction.ymlpackage.json
Pull Request
Related issue(s)
Resolves #57
Description
Summary by CodeRabbit