From 5c023f5142864d6f0a67ee4b06e731518e1684e2 Mon Sep 17 00:00:00 2001 From: Hojeong Park Date: Sun, 31 May 2026 13:11:53 +0900 Subject: [PATCH] doc: update npm supported versions link Signed-off-by: Hojeong Park --- doc/contributing/releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index e2eba8880b1db9..9c5ab59cbc51a4 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -1338,7 +1338,7 @@ branch. This branch will contain the draft release commit (with the draft changelog). Notify the `@nodejs/npm` team in the release proposal PR to inform them of the -upcoming release. `npm` maintains a list of [supported versions](https://github.com/npm/cli/blob/latest/lib/utils/unsupported.js#L3) +upcoming release. `npm` maintains a list of [supported versions](https://github.com/npm/cli/blob/latest/lib/cli/validate-engines.js#L5) that will need updating to include the new major release. To keep the branch in sync until the release date, it can be as simple as