HARMONY-2376: Update Node to 22.23.0

[chris-durbin]

Jira Issue ID

HARMONY-2376

Description

Updates the minor version of node from 22.14.0 to 22.23.0. This is the version we have running in all environments now.

Local Test Steps

nvm install && nvm use
npm ci
npm run build && npm run build-all

• Verify you are now using 22.23.0 - check with node -v
• Verify the docker image builds are successful.
• Verify tests are passing.
• Verify requests continue to work with harmony in a box.

PR Acceptance Checklist

• Acceptance criteria met
• Tests added/updated (if needed) and passing
• Documentation updated (if needed)
• Harmony in a Box tested (if changes made to microservices or new dependencies added)

Summary by CodeRabbit

• Chores
  • Updated the required Node.js and npm versions across the project to newer releases.
  • Refreshed the local development setup guide to match the updated version examples.
  • Bumped the Node.js version reference used by the repository configuration.

[coderabbitai]

Warning

Review limit reached

@chris-durbin, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 55 minutes and 46 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4d46f649-6376-40b3-8a73-4b26f956b36b

📥 Commits

Reviewing files that changed from the base of the PR and between 1494c2b and 177d548.

📒 Files selected for processing (4)

• .github/workflows/ci-tests.yml
• .github/workflows/compare-services.yml
• .github/workflows/harmony-in-a-box.yml
• .github/workflows/publish.yml

📝 Walkthrough

Walkthrough

Node.js runtime version is bumped from 22.14.0 to 22.23.0 and the minimum npm requirement is raised from >=8 to >=10. Changes apply to .nvmrc, the engines field in the root package.json and all service/util package manifests, and the developer setup guide sample output.

Changes

Node.js and npm version bump

Layer / File(s)	Summary
Engine version constraints across all packages .nvmrc, package.json, packages/util/package.json, services/*/package.json	.nvmrc pin and engines.node/engines.npm fields updated to ^22.23.0 / >=10 in the root package and all eight service/util manifests.
Developer setup guide version samples docs/guides/develop.md	Expected node --version and npm --version sample outputs updated to v22.23.0 and 10.9.8.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• indiejames
• ygliuvt
• flamingbear

Poem

🐇 Hippity-hop, a version anew,
From fourteen to twenty-three, through and through!
npm jumps higher, ten is the floor,
.nvmrc updated, what could ask for more?
The rabbit rejoices — fresh Node on the way! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating Node to 22.23.0.
Description check	✅ Passed	The description matches the template and includes the Jira ID, summary, local test steps, and acceptance checklist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch harmony-2376

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.nvmrc:
- Line 1: The Node version bump is only applied in .nvmrc, while the CI workflow
still pins the old 22.14.x release, so the environments remain inconsistent.
Update the Node matrix/version in the .github/workflows/ci-tests.yml workflow to
22.23.x to match the new .nvmrc value, and verify any related Node setup steps
use the same version source.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c8b035d6-3342-46e7-a5ab-f15ad69f1417

📥 Commits

Reviewing files that changed from the base of the PR and between f3bf1fb and 1494c2b.

⛔ Files ignored due to path filters (9)

• package-lock.json is excluded by !**/package-lock.json
• packages/util/package-lock.json is excluded by !**/package-lock.json
• services/cron-service/package-lock.json is excluded by !**/package-lock.json
• services/harmony/package-lock.json is excluded by !**/package-lock.json
• services/query-cmr/package-lock.json is excluded by !**/package-lock.json
• services/service-runner/package-lock.json is excluded by !**/package-lock.json
• services/work-failer/package-lock.json is excluded by !**/package-lock.json
• services/work-scheduler/package-lock.json is excluded by !**/package-lock.json
• services/work-updater/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (11)

• .nvmrc
• docs/guides/develop.md
• package.json
• packages/util/package.json
• services/cron-service/package.json
• services/harmony/package.json
• services/query-cmr/package.json
• services/service-runner/package.json
• services/work-failer/package.json
• services/work-scheduler/package.json
• services/work-updater/package.json

[flamingbear]

Able to build and deploy the images and run requests. I can see the tests are still passing. Nice.

❯ node -v
v22.23.0