chore: update Node.js version to 22 across configuration files

[gliptak]

Node 20 going EOL https://nodejs.org/en/about/previous-releases

Summary by CodeRabbit

• Chores
  • Updated minimum Node.js requirement to 22 across the development environment, CI workflows, and package configuration.
  • Aligned the development container image and CI Node setup with the new Node.js version to ensure consistent toolchain and runtime.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 397002af-5992-4cb0-b53d-fdfbcfb43194

📥 Commits

Reviewing files that changed from the base of the PR and between 9c6bcf7 and 0c99cf7.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• .devcontainer/devcontainer.json
• .github/workflows/ci.yml
• openspec/config.yaml
• package.json

✅ Files skipped from review due to trivial changes (3)

• .devcontainer/devcontainer.json
• openspec/config.yaml
• .github/workflows/ci.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

---

📝 Walkthrough

Walkthrough

Node.js runtime version updated from 20 to 22 across the development environment, CI workflows, and package configuration files. All version constraints and base images are synchronized to the new requirement without functional code changes.

Changes

Cohort / File(s)	Summary
Node.js Version Bump .devcontainer/devcontainer.json, .github/workflows/ci.yml, openspec/config.yaml, package.json	Updated Node.js runtime requirement from 20/>=20.19.0 to 22/>=22.0.0 across devcontainer image, GitHub Actions Node setup, openspec context, and package engines. No other changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 I hopped from twenty to twenty-two with glee,
Config carrots aligned for all to see.
Base image, CI, and engines too,
Synchronized steps for a smoother view.
— a rabbit, nibbling an update or two 🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: updating Node.js version to 22 across configuration files, which is reflected in all four modified files.
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

---

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

[coderabbitai]

🧹 Nitpick comments (1)

.github/workflows/ci.yml (1)

63-63: Optional: centralize Node version to reduce drift risk.

You can define one workflow-level env (for example NODE_VERSION: '22') and reference it in each setup-node step to avoid future partial updates.

Also applies to: 119-119, 158-158, 262-262

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml at line 63, Centralize the Node version by adding a
workflow-level env like NODE_VERSION: '22' and update each setup-node step to
use that env value instead of hardcoding node-version: '22' (replace occurrences
of the node-version field in the setup-node actions with the env reference ${{
env.NODE_VERSION }}); update all instances including the current one and the
additional occurrences noted (lines referenced in the comment) so all setup-node
steps consistently pull from NODE_VERSION.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/workflows/ci.yml:
- Line 63: Centralize the Node version by adding a workflow-level env like
NODE_VERSION: '22' and update each setup-node step to use that env value instead
of hardcoding node-version: '22' (replace occurrences of the node-version field
in the setup-node actions with the env reference ${{ env.NODE_VERSION }});
update all instances including the current one and the additional occurrences
noted (lines referenced in the comment) so all setup-node steps consistently
pull from NODE_VERSION.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6fec0fec-8b46-4553-829b-3c0217a90764

📥 Commits

Reviewing files that changed from the base of the PR and between f529b25 and 9c6bcf7.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• .devcontainer/devcontainer.json
• .github/workflows/ci.yml
• openspec/config.yaml
• package.json

[gliptak]

@TabishB please approve workflow runs