chore: update to node 24

[Nr9]

Greptile Overview

Greptile Summary

Updates the project's Node.js version from 22.21.1 to 24.12.0 in .tool-versions for local development tooling. Adjusts Renovate's allowedVersions constraint in .github/renovate.json5 from <23.0.0 to <25.0.0 to permit future automatic updates to Node 24.x releases.

Confidence Score: 4/5

• Safe to merge; configuration-only change with minimal risk
• This PR updates Node.js version configuration files without modifying application code. The changes are consistent (.tool-versions specifies 24.12.0, renovate.json5 permits <25.0.0), and Node 24 is compatible with the existing package.json engines constraint (">= 22"). The only minor consideration is whether the engines field should be updated to explicitly require Node 24, but this doesn't block the merge.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
.tool-versions	4/5	Updates Node.js from 22.21.1 to 24.12.0; compatible with package.json engines constraint
.github/renovate.json5	5/5	Updates Renovate's allowedVersions constraint from <23.0.0 to <25.0.0 to permit Node 24.x updates

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

package.json
Consider updating the engines constraint to ">= 24" to match the new Node.js version in .tool-versions. While ">= 22" still permits Node 24, explicitly requiring 24 would prevent accidental use of Node 22 or 23 and make the minimum requirement clearer.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}