chore: release 11.7.0

[github-actions]

🤖 I have created a release beep boop

11.7.0

11.7.0 (2025-12-04)

Features

• b380d15 #8697 add deduping to notices unless in verbose+ mode (@owlstronaut)

Bug Fixes

• 35e8d38 #8322 properly handle newlines with input when using the spinner (fix: properly handle newlines with input when using the spinner #8322) (@mbtools)
• 0c0faae #8780 adduser: improve email prompt (fix(adduser): improve email prompt #8780) (@mbtools)

Documentation

• 2030250 #8822 scripts: clarify prepare script runs with --production (Max Black)
• 33a50d7 #8821 scripts: update npm_package_* environment variables documentation (Max Black)
• 50508f9 #8793 package-json: add documentation for type field (docs(package-json): add documentation for type field #8793) (@MaxBlack-dev, Max Black)
• aa1dd7e #8823 scripts: document that prepare scripts run concurrently in workspaces (Max Black)
• 3f48487 #8820 package-spec: fix alias syntax in examples (Max Black)
• dd104da #8812 version: add note about git version requirements (Max Black)
• 58afdcc #8792 install: clarify prerelease version range behavior (Max Black)
• 9f818e8 #8795 npm-view: clarify object property access syntax and provide examples (Max Black)
• 39c2f2e #8791 add examples for command line flags including --prefix (Max Black)
• 1298530 #8790 clarify version field can be omitted in package-lock (Max Black)
• 090b6ca #8794 npx: clarify that arguments are passed to executed command (Max Black)
• a864f80 #8787 document gypfile field in package.json (Max Black)
• 2fc689d #8788 add field access patterns to npm view (Max Black)
• 4850639 #8796 package-json: add examples for replacing dependencies with forks in overrides (Max Black)
• 4864dd4 #8798 npm-install: document engines field priority when installing packages (Max Black)
• 95d25cd #8799 package-json: clarify repository field normalization during publish (Max Black)
• a367f9b #8800 package-lock-json: clarify that version field may be omitted for certain dependencies (Max Black)
• ffc9b71 #8801 npm-install: clarify --tag does not override package.json (docs(npm-install): clarify --tag does not override package.json #8801) (@MaxBlack-dev, Max Black)
• 73688ca #8735 clarify npm version behavior with prerelease versions (docs: clarify npm version behavior with prerelease versions #8735) (@yashwantbezawada)
• 4a32606 #8785 updates the token create documentation (docs: updates the token create documentation #8785) (@owlstronaut, @wraithgar)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/19941706149

Release Checklist for v11.7.0

• 1. Checkout the release branch

  Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

  gh pr checkout 8784 --force

  npm run resetdeps

  node scripts/git-dirty.js

• 2. Check CI status

  gh pr checks --watch

• 3. Publish the CLI and workspaces

  Warning:
  This will publish all updated workspaces to latest, prerelease or backport depending on their version, and will publish the CLI with the dist-tag set to next-11.

  Note:
  The --test argument can optionally be omitted to run the publish process without running any tests locally.

  node scripts/publish.js --test

• 4. Optionally install and test npm@11.7.0 locally

  npm i -g npm@11.7.0

  npm --version
  npm whoami
  npm help install
  # etc

• 5. Set latest dist-tag to newly published version

  Warning:
  NOT FOR PRERELEASE: Do not run this step for prereleases or if 11 is not being set to latest.

  node . dist-tag add npm@11.7.0 latest

• 6. Trigger docs.npmjs.com update

  gh workflow run update-cli.yml --repo npm/documentation

• 7. Approve and Merge release PR

  gh pr review --approve

  gh pr merge --rebase

  git checkout latest

  git fetch

  git reset --hard origin/latest

  node . run resetdeps

• 8. Wait For Release Tags

  Warning:
  The remaining steps all require the GitHub tags and releases to be created first. These are done once this PR has been labelled with autorelease: tagged.

  Release Please will run on the just merged release commit and create GitHub releases and tags for each package. The release bot will will comment on this PR when the releases and tags are created.

  Note:
  The release workflow also includes the Node integration tests which do not need to finish before continuing.

  You can watch the release workflow in your terminal with the following command:

  gh run watch `gh run list -R npm/cli -w release -b latest -L 1 --json databaseId -q ".[0].databaseId"`
  

• 9. Mark GitHub Release as latest

  Warning:
  You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.

  Release Please will make GitHub Releases for the CLI and all workspaces, but GitHub has UI affordances for which release should appear as the "latest", which should always be the CLI. To mark the CLI release as latest run this command:

  gh release -R npm/cli edit v11.7.0 --latest

• 10. Open nodejs/node PR to update npm to latest

  Warning:
  You must wait for CI to create the release tags before running this step. These are done once this PR has been labelled with autorelease: tagged.

  Trigger the Create Node PR action. This will open a PR on nodejs/node to the main branch.

  Note:
  The resulting PR may need to be labelled if it is not intended to land on old Node versions.

  First, sync our fork of node with the upstream source:

  gh repo sync npm/node --source nodejs/node --force

  Then, if we are opening a PR against the latest version of node:

  gh workflow run create-node-pr.yml -f spec=next-11

  If the PR should be opened on a different branch (such as when doing backports) then run it with -f branch=<BRANCH_NAME>. There is also a shortcut to target a specific Node version by specifying a major version number with -f branch=18 (or similar).

  For example, this will create a PR on nodejs/node to the v16.x-staging branch:

  gh workflow run create-node-pr.yml -f spec=next-11 -f branch=16

• 11. Label and fast-track nodejs/node PR

  Note:
  This requires being a nodejs collaborator. This could be you!

  • Thumbs-up reaction on the Fast-track comment
  • Add an LGTM / Approval
  • Add request-ci label to get it running CI
  • Add commit-queue label once everything is green