Repository navigation
chore(node): bump minimum Node.js runtime from >=18 to >=20 - #5
Merged
Merged
Conversation
Node.js 18 reached end-of-life in April 2025. The repo's own `.nvmrc` already targets v22.15.1 and CI runs Node 22, but the package metadata and user-facing prerequisite still advertise v18 as the supported floor. This brings the published minimum in line with what we actually test: - `landing/package.json` — add `engines.node: ">=20"` (previously absent) - `README.md` — bump the Prerequisites bullet from `Node.js (>= v18.0.0)` to `Node.js (>= v20.0.0)` Documentation for the Neon MCP Server overview page needs the matching update: the "Local" setup tab on https://neon.com/docs/ai/neon-mcp-server currently lists `Requires: Node.js >= v18` and should be bumped to `>= v20`. Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Node.js 18 reached end-of-life in April 2025. The repo's own
.nvmrcalready targets v22.15.1 and CI runs Node 22, but the package metadata and user-facing prerequisite still advertise v18 as the supported floor.This brings the published minimum in line with what we actually test:
landing/package.json— addengines.node: ">=20"(previously absent)README.md— bump the Prerequisites bullet fromNode.js (>= v18.0.0)toNode.js (>= v20.0.0)Documentation for the Neon MCP Server overview page needs the matching update: the "Local" setup tab on
https://neon.com/docs/ai/neon-mcp-server currently lists
Requires: Node.js >= v18and should be bumped to>= v20.