Declare Node 24 in engines

[silveltman]

Sets engines.node to >=24.11.0 <25, matching .nvmrc (24), so pnpm flags a local Node version outside 24.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Compatibility
  • The supported Node.js runtime range is now 24.11.0 or later within the 24.x series. Versions earlier than 24.11.0 and versions 25 or later are outside the declared supported range. No changes to application features or behavior are included in this update.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 5e11d688-940a-4e83-a724-559729bbc78d

📥 Commits

Reviewing files that changed from the base of the PR and between 014d38d and 77d3d82.

📒 Files selected for processing (1)

• package.json

Limit details: You’ve used all 10 included reviews currently available.

---

📝 Walkthrough

Walkthrough

The engines.node requirement in package.json changes from >=22.18.0 to >=24.11.0 <25.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 77d3d

The declared Node 24 requirement matches the version selected by CI and release, with no identified issue requiring a change before merge.

Security Architecture Review

Security architecture risk: ⚪ Minimal · up to 77d3d

The change does not expand permissions or alter credential handling. An incompatible Node version could block installation, but the release workflow does not bypass installation failure.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The demonstrated effect reaches root-project runtime eligibility and its CI and release consumers. The change does not establish a new tenant, data-store, network, or credential access path.

Trust Boundaries and Controls

• observed — The existing release workflow creates a GitHub App token from configured credentials and has contents, pull-request, and identity-token write permissions. These authorities predate this manifest-only change; the engine declaration does not modify their configuration.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: declaring Node 24 in the package engine requirements.
Description check	✅ Passed	The description directly explains the engine constraint and its alignment with .nvmrc and pnpm version checks.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

Usage-based review receipt

• Mode: Continue automatically
• Reviewed files: 1
• Waived: $0.25 (charged $0.00)
• View usage details

Note

This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews.

---

_{Comment @coderabbitai help to get the list of available commands.}