docs: link runtime prerequisites instead of restating versions - #2518
Conversation
The getting-started prerequisites listed 'Node.js 20+', but the Node SDK requires '^20.19.0 || >=22.12.0', so 20.0-20.18 and all of 21.x fail to install. nodejs/README.md already states the real constraint. Point each language at the Prerequisites section of its own README, matching how docs/setup/bundled-cli.md now refers to them, so there is one place per SDK to keep current.
There was a problem hiding this comment.
🟢 Approval recommended
All links resolve to prerequisite sections that state the relevant runtime requirements.
Pull request overview
Replaces duplicated runtime versions with links to each SDK’s authoritative prerequisites.
Changes:
- Links all six language SDK prerequisite sections.
- Prevents runtime requirements from drifting across documentation.
File summaries
| File | Description |
|---|---|
docs/getting-started.md |
References SDK-specific runtime prerequisites. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
SteveSandersonMS
left a comment
There was a problem hiding this comment.
Verified: nodejs/package.json requires ^20.19.0 || >=22.12.0, so the old "Node.js 20+" line in getting-started.md was inaccurate (20.0-20.18 and 21.x actually fail with EBADENGINE), and the .NET line was similarly off. Confirmed all six linked README.md#prerequisites anchors resolve, and this matches the existing pattern in docs/setup/bundled-cli.md. Small, correct, prose-only fix. Approving.
Summary
The getting-started prerequisites say Node.js 20+, but the Node SDK declares:
So 20.0-20.18 and all of 21.x are unsupported, and a reader who follows this page onto one of them hits
EBADENGINEat install time.nodejs/README.mdalready states the real constraint, so the list on this page had simply drifted.Rather than correcting the number and leaving a second copy to drift again, this points each language at the Prerequisites section of its own README - the same thing
docs/setup/bundled-cli.mdnow does. That keeps one source of truth per SDK.Verification
## Prerequisitesheading, and the../<lang>/README.mdpaths resolve fromdocs/.^20.19.0 || >=22.12.0, Python>=3.11, Go1.24, Rust1.94.0, Java 17 (JDK 25 recommended), .NET any .NET Standard 2.0-compatible implementation. The removed line also understated .NET, which targetsnetstandard2.0in addition tonet8.0/net10.0.docs-validateis unaffected.