feat: preparation for v12#2000
Merged
Merged
Conversation
Add a v12 release entry pointing at the `latest` branch and repoint v11 to its new `release/v11` branch, mirroring the previous major prep (v10/v11). Without a v12 entry the docs build never matches npm@12.x, so no v12 CLI documentation is generated. Fixes npm/cli#9742 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: bfe56b28-0e89-4026-aa38-ebf121659ae5
dhei
approved these changes
Jul 10, 2026
nishantms
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Situation
npm@12.0.0 was released, but no CLI documentation was generated for v12 (see npm/cli#9742). https://docs.npmjs.com/cli still redirects to v11.
Root cause
The nightly Update CLI workflow only runs
npm run build -w cli, which reads the manually-maintainedcli/releases.json. That file had nov12entry, sobuild.jsnever matchednpm@12.xto a release and generated nothing. Additionallyv11still pointed at thelatestbranch, which now tracks v12 in npm/cli.Change
Repoint
v11to its newrelease/v11branch and add av12entry onlatest, mirroring the previous major preparations ("Update CLI releases for npm 10" and #1402 "preparation for v11").Adding the new
v12key triggers the build's cache-voiding (voidOnNewKey), which resets v11 tolegacyand regenerates the nav. After merge, the nightlyupdate-clijob (or a manualworkflow_dispatch) will build and publish the v12 docs.Fixes npm/cli#9742