Skip to content

feat: add Upgrading Node.js info page with navigation and EOL CTAs#1

Draft
edsadr wants to merge 2 commits into
mainfrom
feat/upgrading-nodejs-page
Draft

feat: add Upgrading Node.js info page with navigation and EOL CTAs#1
edsadr wants to merge 2 commits into
mainfrom
feat/upgrading-nodejs-page

Conversation

@edsadr

@edsadr edsadr commented Jun 15, 2026

Copy link
Copy Markdown
Member

Summary

This PR adds a new Upgrading Node.js page under /about/upgrading-nodejs with:

  • A new page providing guidance on upgrading Node.js versions
  • A CTA on the EOL page linking to the new page (replaces the direct download link)
  • Navigation entry in navigation.json
  • i18n labels in en.json
  • NodeSourceLogo component registration
  • @nodejs/doc-kit added to pnpm-workspace.yaml allowBuilds

Goal

This is a starting point — we would like to invite the Node.js Userland Migrations Working Group to collaborate, refine, and own the final version of this page for inclusion in the official Node.js website.

The intention is to provide a canonical resource that helps users assess their upgrade readiness, understand breaking changes, and plan migrations — something the Node.js community has long needed.

What is Next?

We are opening this early to gather feedback from the working group and the broader community. The content, design, and tooling integrations are all open for discussion.


This is a draft PR — ready for collaboration, not merge.

@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 45589bcb-45eb-42af-9916-bd4162f7bdfc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/upgrading-nodejs-page

Comment @coderabbitai help to get the list of available commands and usage tips.

@edsadr edsadr force-pushed the feat/upgrading-nodejs-page branch from 8f201f4 to d3a2e27 Compare June 15, 2026 20:51
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