cli chore: release 10.8.2

:robot: I have created a release beep boop

10.8.2

10.8.2 (2024-06-27)

Bug Fixes

2273183 #7595 outdated: fixed wanted range for alias with version range (#7595) (@milaninfy)

Documentation

ac937d4 #7616 install: add save-peer flag (#7616) (@drew4237)
55639ef #7615 use git+https in package.com url examples (#7615) (@MikeMcC399)
93883bb #7582 Improve manpage section for package.json funding properties (#7582) (@kemitchell)
92e71e6 #7576 fix links to community discussions (#7576) (@leobalter)

Dependencies

e5451e1 #7605 [email protected]
7b584d3 #7605 [email protected]
941d0d7 #7605 [email protected]
8b8ce7a #7605 [email protected]
4646768 #7605 [email protected]
6f0d7ce #7605 @npmcli/[email protected]
29204c8 #7605 @npmcli/[email protected]
04d6910 #7574 @npmcli/[email protected]
4ef4830 #7574 remove read-package-json-fast

10.8.2 (2024-06-27)

Bug Fixes

2273183 #7595 outdated: fixed wanted range for alias with version range (#7595) (@milaninfy)

Documentation

ac937d4 #7616 install: add save-peer flag (#7616) (@drew4237)
55639ef #7615 use git+https in package.com url examples (#7615) (@MikeMcC399)
93883bb #7582 Improve manpage section for package.json funding properties (#7582) (@kemitchell)
92e71e6 #7576 fix links to community discussions (#7576) (@leobalter)

Dependencies

e5451e1 #7605 [email protected]
7b584d3 #7605 [email protected]
941d0d7 #7605 [email protected]
8b8ce7a #7605 [email protected]
4646768 #7605 [email protected]
6f0d7ce #7605 @npmcli/[email protected]
29204c8 #7605 @npmcli/[email protected]
04d6910 #7574 @npmcli/[email protected]
4ef4830 #7574 remove read-package-json-fast

Chores

3b8b111 #7605 update devDependencies in lockfile (@wraithgar)

Chores

3b8b111 #7605 update devDependencies in lockfile (@wraithgar)

arborist: 7.5.4

7.5.4 (2024-06-27)

Bug Fixes

a8e666e #7602 arborist: condition to include name field in package-lock fixed (#7602) (@milaninfy)

config: 8.3.4

8.3.4 (2024-06-27)

Bug Fixes

15be6dd #7574 don't try parsing workspaces if none exist (@wraithgar)
d185c9b #7574 use @npmcli/package-json to parse local package (@wraithgar)

Dependencies

04d6910 #7574 @npmcli/[email protected]
4ef4830 #7574 remove read-package-json-fast

libnpmdiff: 6.1.4

Dependencies

workspace: @npmcli/[email protected]

libnpmexec: 8.1.3

8.1.3 (2024-06-27)

Bug Fixes

71c6848 #7587 exec: npx to run specified version if multiple version exist globally (#7587) (@milaninfy)

Dependencies

workspace: @npmcli/[email protected]

libnpmfund: 5.0.12

Dependencies

workspace: @npmcli/[email protected]

libnpmpack: 7.0.4

Dependencies

workspace: @npmcli/[email protected]

This PR was generated with Release Please. See documentation.

May 30 '24 15:05 github-actions[bot]

Release Manager

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

Release Checklist for v10.8.2

[ ] 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 7575 --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 [email protected] locally

npm i -g [email protected]

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 [email protected] 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.8.2 --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. 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

May 30 '24 15:05 github-actions[bot]

:robot: Release is at https://github.com/npm/cli/releases/tag/v10.8.2 :sunflower: