Upgrade Node.js from 18 to 20 across build, test, website and repo#10050
Merged
chrisgervang merged 3 commits intomasterfrom Feb 27, 2026
Merged
Upgrade Node.js from 18 to 20 across build, test, website and repo#10050chrisgervang merged 3 commits intomasterfrom
chrisgervang merged 3 commits intomasterfrom
Conversation
- Update .nvmrc from 18.20.8 to 20.19.0 (Node 20 LTS) - Update package.json engines field from >=14 to >=18 - Update CONTRIBUTING.md to document >=20 requirement - Update Dockerfile base image from node:8.9.0 to node:20 CI workflows already use node-version-file: '.nvmrc' so they will automatically pick up the new Node 20 version. https://claude.ai/code/session_016oyFSyGm7hYU1e1KDXqjnW
The root package.json and CONTRIBUTING.md already document Node >=20 as the required version, and CI picks it up via .nvmrc. This adds the same constraint to the website sub-package so it is explicit there too. https://claude.ai/code/session_016oyFSyGm7hYU1e1KDXqjnW
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Pessimistress
approved these changes
Feb 27, 2026
Aligns with CONTRIBUTING.md and website/package.json which both already require Node >=20. The root package is private so this reflects the dev environment requirement, not a published constraint. https://claude.ai/code/session_016oyFSyGm7hYU1e1KDXqjnW
Pessimistress
pushed a commit
that referenced
this pull request
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI workflows already use node-version-file: '.nvmrc' so they
will automatically pick up the new Node 20 version.
https://claude.ai/code/session_016oyFSyGm7hYU1e1KDXqjnW
Note
Medium Risk
Medium risk because it raises the minimum Node version for local dev/build/test and updates the Docker base image, which can surface compatibility issues in CI and contributor environments. No application/runtime logic changes are included.
Overview
Upgrades the repository’s Node.js baseline to Node 20 by updating
.nvmrc, tighteningpackage.jsonandwebsite/package.jsonengines.noderequirements, and refreshing contributor docs to reflect the new minimum version.Updates the
Dockerfilebase image from an old Node release tonode:20, aligning containerized builds/tests with the new tooling baseline.Written by Cursor Bugbot for commit 176a4f2. This will update automatically on new commits. Configure here.