chore: release 10.6.0

[github-actions]

🤖 I have created a release beep boop

10.6.0

10.6.0 (2024-04-25)

Features

• 9123de4 #7373 do all ouput over proc-log events (@lukekarrys)
• 9622597 #7339 refactor terminal display (feat: refactor terminal display #7339) (@lukekarrys)

Bug Fixes

• 0e74ee4 #7416 clean up npm object (fix: clean up npm object #7416) (@wraithgar)
• c060e60 #7415 return command and argv from load (@lukekarrys)
• 180b919 #7415 remove unused npm.setCmd method (@lukekarrys)
• 0708b3b #7414 use name of level instead of label for logging prefixes (fix: use name of level instead of label for logging prefixes #7414) (@lukekarrys)
• 7f4e667 #7403 redact when displaying non-ascii arguments (@lukekarrys)
• 06202f0 #7403 store unref promises for awaiting in tests (@lukekarrys)
• e5f1948 #7403 run update notifier after exec but before waiting (@lukekarrys)
• f309c1c #7403 refactor: move timer and error logfile messages to lib/npm (@lukekarrys)
• 43e6194 #7403 dont show run script banners in silent (@lukekarrys)
• 694dba9 #7403 dont expose as many public properties of timers (@lukekarrys)
• 7ca6d84 #7403 use proc-log META for flush and force (@lukekarrys)
• 2538438 #7403 dont write timing logs to file unless requested (@lukekarrys)
• 7e04417 #7403 rename base-cmd to match other commands (@lukekarrys)
• fc68547 #7403 remove some npm.load timers and exit earlier for --versions (@lukekarrys)
• 28019d5 #7403 cleanup: move cli specific files to separate dir (@lukekarrys)
• 469f788 #7403 cleanup: newlines and whitespace (@lukekarrys)
• 4ab6401 #7403 cleanup: dont nest files utils dir (@lukekarrys)
• 78447d7 #7399 prefer fs/promises over promisify (fix: prefer fs/promises over promisify #7399) (@lukekarrys)
• d531f8b #7407 Remove table output from search and tar summary (@wraithgar)
• c209e98 #7401 Remove table output from many commands (@wraithgar)
• ad7ab8c #7388 perf: lazy loading optimizations (fix(perf): lazy loading optimizations #7388) (@wraithgar)
• 8eae4b3 #7385 token: properly await registry request (fix(token): properly await registry request #7385) (@wraithgar)
• 9216d59 #7377 better output colors (fix: better output colors #7377) (@wraithgar)
• 6512112 #7378 use proc-log for all timers (@lukekarrys)
• 2a80dab #7370 typo in npm access usage (fix: typo in npm access usage #7370) (@mbtools)

Documentation

• dfa4cab #7401 update output examples (@wraithgar)
• 140b9c9 #7382 package-json: note that line endings are inferred (docs(package-json): note that line endings are inferred #7382) (@ertw)
• c16dd4e #7367 Document that overrides only work in the root package.json (docs: Document that overrides only work in the root package.json #7367) (@s100)

Dependencies

• 36adff3 #7408 pacote@18.0.2
• 486d46c #7408 @npmcli/installed-package-contents@2.1.0
• 157d0ae #7408 @npmcli/package-json@5.1.0
• b0ca163 #7409 remove @npmcli/disparity-colors
• c77f035 #7407 remove columnify
• 2ec690d #7401 move cli-table3 to devDependencies
• fc6e291 #7392 proc-log@4.2.0 (deps: proc-log@4.2.0 #7392)
• 38ed048 #7378 @npmcli/metavuln-calculator@7.1.0
• 7678a3d #7378 proc-log@4.1.0
• 87f6c09 #7373 @npmcli/metavuln-calculator@7.0.1
• b8f8b41 #7373 @npmcli/run-script@8.0.0
• 79f79c7 #7373 proc-log@4.0.0
• 9027266 #7373 pacote@18.0.0
• ee4b3e0 #7373 npm-registry-fetch@16.2.1
• 0e7789b #7373 npm-profile@9.0.1
• ac98fd3 #7373 npm-package-arg@11.0.2
• 9351570 #7373 @npmcli/package-json@5.0.3
• d3a0cfa #7373 @npmcli/git@5.0.6
• workspace: @npmcli/arborist@7.5.0
• workspace: @npmcli/config@8.3.0
• workspace: libnpmaccess@8.0.4
• workspace: libnpmdiff@6.1.0
• workspace: libnpmexec@8.0.0
• workspace: libnpmfund@5.0.8
• workspace: libnpmhook@10.0.3
• workspace: libnpmorg@6.0.4
• workspace: libnpmpack@7.0.0
• workspace: libnpmpublish@9.0.6
• workspace: libnpmsearch@7.0.3
• workspace: libnpmteam@6.0.3
• workspace: libnpmversion@6.0.0

Chores

• 3cbc258 #7403 test for early version exit (@lukekarrys)
• 08e0c0e #7403 move sigstore json files to fixtures dir (@lukekarrys)
• ea66e95 #7380 remove licensee as a devDependency (chore: remove licensee as a devDependency #7380) (@lukekarrys, @wraithgar)
• 9333e9d #7386 reduce windows shim test flakes (chore: reduce windows shim test flakes #7386) (@lukekarrys)

arborist: 7.5.0

7.5.0 (2024-04-25)

Features

• 9123de4 #7373 do all ouput over proc-log events (@lukekarrys)
• 9622597 #7339 refactor terminal display (feat: refactor terminal display #7339) (@lukekarrys)

Bug Fixes

• 78447d7 #7399 prefer fs/promises over promisify (fix: prefer fs/promises over promisify #7399) (@lukekarrys)
• 6512112 #7378 use proc-log for all timers (@lukekarrys)

Dependencies

• 36adff3 #7408 pacote@18.0.2
• 486d46c #7408 @npmcli/installed-package-contents@2.1.0
• 157d0ae #7408 @npmcli/package-json@5.1.0
• fc6e291 #7392 proc-log@4.2.0 (deps: proc-log@4.2.0 #7392)
• 38ed048 #7378 @npmcli/metavuln-calculator@7.1.0
• 7678a3d #7378 proc-log@4.1.0
• 87f6c09 #7373 @npmcli/metavuln-calculator@7.0.1
• b8f8b41 #7373 @npmcli/run-script@8.0.0
• 79f79c7 #7373 proc-log@4.0.0
• 9027266 #7373 pacote@18.0.0
• ee4b3e0 #7373 npm-registry-fetch@16.2.1
• ac98fd3 #7373 npm-package-arg@11.0.2
• 9351570 #7373 @npmcli/package-json@5.0.3

Chores

• dd39de7 #7411 disable selflink test on apple silicon (chore: disable selflink test on apple silicon #7411) (@lukekarrys)

config: 8.3.0

8.3.0 (2024-04-25)

Features

• 9123de4 #7373 do all ouput over proc-log events (@lukekarrys)

Bug Fixes

• 03634be #7403 remove granular config timers (@lukekarrys)
• 78447d7 #7399 prefer fs/promises over promisify (fix: prefer fs/promises over promisify #7399) (@lukekarrys)
• 6512112 #7378 use proc-log for all timers (@lukekarrys)

Dependencies

• fc6e291 #7392 proc-log@4.2.0 (deps: proc-log@4.2.0 #7392)
• 7678a3d #7378 proc-log@4.1.0
• 79f79c7 #7373 proc-log@4.0.0
• 9027266 #7373 pacote@18.0.0

libnpmaccess: 8.0.4

8.0.4 (2024-04-25)

Dependencies

• ee4b3e0 #7373 npm-registry-fetch@16.2.1
• ac98fd3 #7373 npm-package-arg@11.0.2

libnpmdiff: 6.1.0

6.1.0 (2024-04-25)

Features

• 9622597 #7339 refactor terminal display (feat: refactor terminal display #7339) (@lukekarrys)

Bug Fixes

• 03958c3 #7409 inline color selector in libnpmdiff (@wraithgar)

Dependencies

• 36adff3 #7408 pacote@18.0.2
• 486d46c #7408 @npmcli/installed-package-contents@2.1.0
• b0ca163 #7409 remove @npmcli/disparity-colors
• 9027266 #7373 pacote@18.0.0
• ac98fd3 #7373 npm-package-arg@11.0.2
• workspace: @npmcli/arborist@7.5.0

libnpmexec: 8.0.0

8.0.0 (2024-04-25)

⚠️ BREAKING CHANGES

• libnpmexec now emits an output event on process instead of invoking the output function passed in

Features

• 39e4da0 #7373 libnpmexec: no longer accept output function (@lukekarrys)
• 9622597 #7339 refactor terminal display (feat: refactor terminal display #7339) (@lukekarrys)

Dependencies

• 36adff3 #7408 pacote@18.0.2
• fc6e291 #7392 proc-log@4.2.0 (deps: proc-log@4.2.0 #7392)
• 7678a3d #7378 proc-log@4.1.0
• b8f8b41 #7373 @npmcli/run-script@8.0.0
• 79f79c7 #7373 proc-log@4.0.0
• 9027266 #7373 pacote@18.0.0
• ac98fd3 #7373 npm-package-arg@11.0.2
• workspace: @npmcli/arborist@7.5.0

libnpmfund: 5.0.8

5.0.8 (2024-04-25)

Dependencies

• workspace: @npmcli/arborist@7.5.0

libnpmhook: 10.0.3

10.0.3 (2024-04-25)

Dependencies

• ee4b3e0 #7373 npm-registry-fetch@16.2.1

libnpmorg: 6.0.4

6.0.4 (2024-04-25)

Dependencies

• ee4b3e0 #7373 npm-registry-fetch@16.2.1

libnpmpack: 7.0.0

7.0.0 (2024-04-25)

⚠️ BREAKING CHANGES

• libnpmpack no longer takes a silent option to suppress output from @npmcli/run-script. That output is now emitted via an output event on process.

Features

• ee9bf6e #7373 libnpmpack: remove silent option (@lukekarrys)

Bug Fixes

• 78447d7 #7399 prefer fs/promises over promisify (fix: prefer fs/promises over promisify #7399) (@lukekarrys)

Dependencies

• 36adff3 #7408 pacote@18.0.2
• b8f8b41 #7373 @npmcli/run-script@8.0.0
• 9027266 #7373 pacote@18.0.0
• ac98fd3 #7373 npm-package-arg@11.0.2
• workspace: @npmcli/arborist@7.5.0

libnpmpublish: 9.0.6

9.0.6 (2024-04-25)

Dependencies

• fc6e291 #7392 proc-log@4.2.0 (deps: proc-log@4.2.0 #7392)
• 7678a3d #7378 proc-log@4.1.0
• 79f79c7 #7373 proc-log@4.0.0
• ee4b3e0 #7373 npm-registry-fetch@16.2.1
• ac98fd3 #7373 npm-package-arg@11.0.2

libnpmsearch: 7.0.3

7.0.3 (2024-04-25)

Dependencies

• ee4b3e0 #7373 npm-registry-fetch@16.2.1

libnpmteam: 6.0.3

6.0.3 (2024-04-25)

Dependencies

• ee4b3e0 #7373 npm-registry-fetch@16.2.1

libnpmversion: 6.0.0

6.0.0 (2024-04-25)

⚠️ BREAKING CHANGES

• libnpmversion no longer takes a silent option to suppress output from @npmcli/run-script. That output is now emitted via an output event on process.

Features

• 60faa90 #7373 libnpmversion: remove silent option (@lukekarrys)

Bug Fixes

• 78447d7 #7399 prefer fs/promises over promisify (fix: prefer fs/promises over promisify #7399) (@lukekarrys)

Dependencies

• fc6e291 #7392 proc-log@4.2.0 (deps: proc-log@4.2.0 #7392)
• 7678a3d #7378 proc-log@4.1.0
• b8f8b41 #7373 @npmcli/run-script@8.0.0
• 79f79c7 #7373 proc-log@4.0.0
• d3a0cfa #7373 @npmcli/git@5.0.6

---

This PR was generated with Release Please. See documentation.

[github-actions]

Release Manager

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

Release Checklist for v10.6.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 7368 --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-10.

  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@10.6.0 locally

  npm i -g npm@10.6.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 10 is not being set to latest.

  node . dist-tag add npm@10.6.0 latest

• 6. Trigger docs.npmjs.com update

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

• 7. Merge release PR

  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 v10.6.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-10

  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-10 -f branch=16

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

  Note:
  This requires being a nodejs collaborator. Currently @lukekarrys is so ping them to do these steps!

  • 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

[wraithgar]

Test failures in 18.x have to do w/ the test suite, not w/ an actual bug. Tests work in isolation and if coverage is disabled. We still want to track this down but it shouldn't block the release.

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/v10.6.0 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/arborist-v7.5.0 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/config-v8.3.0 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmaccess-v8.0.4 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmdiff-v6.1.0 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmexec-v8.0.0 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmfund-v5.0.8 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmhook-v10.0.3 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmorg-v6.0.4 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmpack-v7.0.0 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmpublish-v9.0.6 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmsearch-v7.0.3 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmteam-v6.0.3 🌻

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/libnpmversion-v6.0.0 🌻

[github-actions]

Release Workflow

• npm@10.6.0 https://github.com/npm/cli/releases/tag/v10.6.0
• @npmcli/arborist@7.5.0 https://github.com/npm/cli/releases/tag/arborist-v7.5.0
• @npmcli/config@8.3.0 https://github.com/npm/cli/releases/tag/config-v8.3.0
• libnpmaccess@8.0.4 https://github.com/npm/cli/releases/tag/libnpmaccess-v8.0.4
• libnpmdiff@6.1.0 https://github.com/npm/cli/releases/tag/libnpmdiff-v6.1.0
• libnpmexec@8.0.0 https://github.com/npm/cli/releases/tag/libnpmexec-v8.0.0
• libnpmfund@5.0.8 https://github.com/npm/cli/releases/tag/libnpmfund-v5.0.8
• libnpmhook@10.0.3 https://github.com/npm/cli/releases/tag/libnpmhook-v10.0.3
• libnpmorg@6.0.4 https://github.com/npm/cli/releases/tag/libnpmorg-v6.0.4
• libnpmpack@7.0.0 https://github.com/npm/cli/releases/tag/libnpmpack-v7.0.0
• libnpmpublish@9.0.6 https://github.com/npm/cli/releases/tag/libnpmpublish-v9.0.6
• libnpmsearch@7.0.3 https://github.com/npm/cli/releases/tag/libnpmsearch-v7.0.3
• libnpmteam@6.0.3 https://github.com/npm/cli/releases/tag/libnpmteam-v6.0.3
• libnpmversion@6.0.0 https://github.com/npm/cli/releases/tag/libnpmversion-v6.0.0
• Workflow run: ❌ https://github.com/npm/cli/actions/runs/8836908777

🚨🚨🚨

@npm/cli-team: The post-release workflow failed for this release. Manual steps may need to be taken after examining the workflow output.

🚨🚨🚨

[wraithgar]

Node.js PR is at nodejs/node#52691