Skip to content

Correct Node.js version for custom CA trust#79

Open
pichuzhkin wants to merge 1 commit into
nodejs:mainfrom
pichuzhkin:patch-1
Open

Correct Node.js version for custom CA trust#79
pichuzhkin wants to merge 1 commit into
nodejs:mainfrom
pichuzhkin:patch-1

Conversation

@pichuzhkin
Copy link
Copy Markdown

22.15 doesn't really support NODE_USE_SYSTEM_CA=1, only 22.19 does, it was tested and it is already documented in https://nodejs.org/api/cli.html#node_use_system_ca1

22.15 doesn't really support NODE_USE_SYSTEM_CA=1, only 22.19 does, it was tested and it is already documented in https://nodejs.org/api/cli.html#node_use_system_ca1

Signed-off-by: Victor Pichuzhkin <79213271+pichuzhkin@users.noreply.github.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 27, 2026

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

Project Deployment Actions Updated (UTC)
nodejs-learn Ready Ready Preview May 27, 2026 9:54pm

Request Review

@cursor
Copy link
Copy Markdown

cursor Bot commented May 27, 2026

PR Summary

Low Risk
Documentation-only version correction with no runtime or API changes.

Overview
Updates the Certificate Authority Configuration section in enterprise-network-configuration.md so the stated minimum versions for NODE_USE_SYSTEM_CA / --use-system-ca match Node’s actual support.

The doc no longer lists v22.15.0, v23.9.0, or v24.0.0 as sufficient; it now says v22.19.0 and v24.6.0 and above, aligning with tested behavior and the official CLI docs.

Reviewed by Cursor Bugbot for commit 4fb58ec. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
Copy link
Copy Markdown

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/http

Please review the changes when you have a chance. Thank you! 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant