From 6e3f03aab00a0f9daa85f402aa6e789a8a5520b5 Mon Sep 17 00:00:00 2001 From: Corey Butler <770982+coreybutler@users.noreply.github.com> Date: Wed, 11 Nov 2026 01:46:01 -0600 Subject: [PATCH] docs: mark legacy latest policy as Governance-only Add the certified governance edition banner and call out Governance-only on cross-links. --- docs/guide/legacy-latest-policy.md | 2 ++ docs/guide/upgrade-from-v1.md | 2 +- docs/guide/version-resolution.md | 2 +- 3 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/guide/legacy-latest-policy.md b/docs/guide/legacy-latest-policy.md index dbe7b4d..ca8eecc 100644 --- a/docs/guide/legacy-latest-policy.md +++ b/docs/guide/legacy-latest-policy.md @@ -2,6 +2,8 @@ title: Legacy latest policy sidebar_label: Legacy latest policy sidebar_position: 2.5 +certified: + edition: governance --- # Legacy latest policy diff --git a/docs/guide/upgrade-from-v1.md b/docs/guide/upgrade-from-v1.md index 214e444..8c27a47 100644 --- a/docs/guide/upgrade-from-v1.md +++ b/docs/guide/upgrade-from-v1.md @@ -65,7 +65,7 @@ After install, open a **new** terminal and run `nvm list` to confirm the version In v2, `nvm install latest` resolves to the newest **stable** Node.js release (it skips prereleases such as alphas). Use `nvm install alpha` for the newest `-alpha*` release. -Governance fleets that must keep tip-of-index `latest` for existing scripts can enable `LatestIncludesPrerelease` — see [Legacy latest policy](./legacy-latest-policy). +**Governance only:** fleets that must keep tip-of-index `latest` for existing scripts can enable `LatestIncludesPrerelease` — see [Legacy latest policy](./legacy-latest-policy). ### Backup in restricted environments diff --git a/docs/guide/version-resolution.md b/docs/guide/version-resolution.md index 160d09a..eddc010 100644 --- a/docs/guide/version-resolution.md +++ b/docs/guide/version-resolution.md @@ -40,7 +40,7 @@ Commands that accept version specifiers include: - `latest` walks the Node.js index and picks the newest row **without** a `-` prerelease suffix. When Node publishes an alpha at the tip of [index.tab](https://nodejs.org/dist/index.tab), `latest` still resolves to the prior stable release so downloads do not invent a missing GA tag. Bare `nvm install` (no version argument) is the same as `nvm install latest`. - `alpha` picks the newest row whose version contains `-alpha` and keeps that full tag (for example `27.0.0-alpha.0.0.0`) for download and install. After `nvm install alpha` succeeds, NVM prints a one-line note that alpha releases are unstable. -Governance fleets that must keep the older tip-of-index meaning of `latest` can enable `LatestIncludesPrerelease`. See [Legacy latest policy](./legacy-latest-policy). +**Governance only:** fleets that must keep the older tip-of-index meaning of `latest` can enable `LatestIncludesPrerelease`. See [Legacy latest policy](./legacy-latest-policy). ### Examples