Update CI to Node 22

[vicb]

Summary by Sourcery

CI:

• Bump GitHub Actions Node.js version to 22.x

Summary by CodeRabbit

• Chores
  • Updated CI to use Node.js 22 (from 20) for automated builds and tests. This aligns with the latest runtime, improving build reliability and future compatibility. No user-facing functionality is changed, and no action is required from end-users.

[coderabbitai]

Walkthrough

The Node.js GitHub Actions workflow matrix was updated to use Node.js 22.x instead of 20.x. All other CI steps and structure remain unchanged, continuing to use the matrix-provided Node.js version.

Changes

Cohort / File(s)	Summary
CI config .github/workflows/node.js.yml	Updated matrix.node-version from 20.x to 22.x; no other workflow steps changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update deps #336 — Updates runtime and @types/node to 22.x, aligning with the CI Node.js 22.x upgrade.
• Use the node LTS release #302 — Pins Node.js to LTS 20.x in images/configs, contrasting with this PR’s CI upgrade to 22.x.

Poem

I twitch my whiskers, bump the ver to new,
From 20 hops to 22 I flew.
Pipelines purr, the checks still run,
Carrots compiled, tests all done.
Thump-thump—CI’s fresh and true! 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "Update CI to Node 22" is concise and directly describes the primary change in the diff—updating the GitHub Actions Node.js matrix from 20.x to 22.x in .github/workflows/node.js.yml—so it clearly communicates the main intent to reviewers.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch vicb/ci-node-22

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1369287 and 0a86256.

📒 Files selected for processing (1)

• .github/workflows/node.js.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Sourcery review
• GitHub Check: Analyze (javascript)
• GitHub Check: build (22.x)

🔇 Additional comments (1)

.github/workflows/node.js.yml (1)

14-14: Upgrade CI to Node 22 LTS — LGTM

Matrix bump to 22.x looks correct and will be honored by actions/setup-node@v4. Please verify ecosystem alignment:

• package.json "engines" (and any Volta/asdf/.nvmrc) updated to 22.
• Any Docker/devcontainer images pinning Node also updated.
• If you still claim runtime support for Node 20, consider a temporary dual-version matrix to catch regressions.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The GitHub Actions workflow for Node.js CI has been updated to run against Node 22.x by adjusting the version matrix in the YAML configuration.

File-Level Changes

Change	Details	Files
CI Node.js version bumped to 22.x	Bumped node-version matrix entry from 20.x to 22.x	.github/workflows/node.js.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}