fix: Fixes node engine to support >=20

[mackenly]

Fixes bug where only node 20, 22, and 24 were supported rather than 20+

Closes #215

Summary by CodeRabbit

• Chores
  • Expanded Node.js version compatibility to support all versions 20.0.0 and above, allowing broader runtime flexibility.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

📝 Walkthrough

Walkthrough

The engines.node constraint in package.json is broadened from 20 || 22 || 24 to >=20, permitting any Node.js version at or above v20 rather than restricting to only specific even-numbered releases.

Changes

Node.js Engine Constraint

Layer / File(s)	Summary
Engine Configuration package.json	engines.node updated from `20

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• parse-community/node-apn#212: This main PR broadens the Node engine constraint to >=20 while the retrieved PR tightened it to 20 || 22 || 24, directly reversing the previous change.
• parse-community/node-apn#186: Both PRs modify the Node engine constraint in package.json to change supported Node versions.

🚥 Pre-merge checks | ✅ 6 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	❓ Inconclusive	Cannot determine if review feedback exists. Only one commit found with no follow-ups suggesting engagement. PR is open but no review comments visible in accessible git history.	Verify PR #216 on GitHub for actual review comments. If none exist, check is not applicable. If they exist, verify author engagement or follow-up commits.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	The PR successfully addresses the objective from issue #215 by changing engines.node from '20 || 22 || 24' to '>=20'.
Out of Scope Changes check	✅ Passed	The PR contains only the necessary change to package.json engines field, with no out-of-scope modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	PR only modifies package.json engines field from "20 || 22 || 24" to ">=20". No code or dependency changes. No security vulnerabilities introduced.
Title check	✅ Passed	The PR title begins with 'fix:' prefix as required and accurately describes the main change - updating Node engine constraint to support >=20 versions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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