build(deps): bump nodejs version from v20.18 to v20.20

[ccamel]

Self explanatory.

(allow the PR #778 to pass)

Summary by CodeRabbit

• Chores
  • Bumped Node.js runtime and package engine from v20.18 to v20.20 across CI workflows and project configuration to ensure consistent build and runtime environments.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Jan 19, 2026 1:20pm

[coderabbitai]

📝 Walkthrough

Walkthrough

Node.js runtime/version constraints bumped from 20.18 to 20.20 across GitHub Actions workflows and package.json; copilot instruction file updated. No functional logic or control-flow changes.

Changes

Cohort / File(s)	Summary
GitHub Workflows .github/workflows/build.yml, .github/workflows/capture-website.yml, .github/workflows/lint.yml, .github/workflows/update-versioned-docs.yml	Updated Setup Node environment node-version values from 20.18 → 20.20 in multiple jobs (build, capture-website, lint, docs).
Repository Metadata & Docs .github/copilot-instructions.md, package.json	Bumped Node version references: copilot instructions and package.json "engines" constraint changed from ^20.18 → ~20.20.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Upgrade Node.js from v18.19 to LTS v20.18 #586 #587: Previously updated Node.js version in the same CI/workflow and package.json locations (to 20.18); closely related change history.

Suggested reviewers

• amimart

Poem

🐰 I hopped through code with a jaunty spring,

Eighteen to twenty—what joy I bring!
Workflows aligned, package.json too,
A tiny bump, fresh and new,
🥕 Pipelines hum a brighter tune.

🚥 Pre-merge checks | ✅ 3

✅ 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 clearly and specifically describes the main change: upgrading Node.js from v20.18 to v20.20 across the codebase.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

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]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@package.json`:
- Around line 13-15: The engines.node field in package.json currently uses a
caret range ("node": "^20.20") which permits minor and patch updates within Node
20 (>=20.20.0 <21.0.0); if you intend to restrict to patch updates only for the
20.20 series, change the value to a tilde range ("node": "~20.20") or explicitly
document the intended upgrade policy in the repo (e.g., a README or package.json
comment) so it's clear whether engines.node should allow 20.21/20.22 or only
20.20.x.

[bot-anik]

Device	URL
desktop	http://localhost:3000/

Device	URL
mobile	http://localhost:3000/

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

[ccamel]

@coderabbitai resolve

[coderabbitai]

✅ Actions performed

Comments resolved.