cli chore: release 10.8.1

:robot: I have created a release beep boop

10.8.1

10.8.1 (2024-05-22)

Bug Fixes

9122fb6 #7516 cache: add both full and minified packument to cache (#7516) (@milaninfy)
9e6686b #7545 send proper otp token on web auth (#7545) (@wraithgar)
b1db070 #7534 refactor: use output.buffer and set explicit json mode in query (#7534) (@lukekarrys)
53cda32 #7542 refactor ls to use output.buffer for json (#7542) (@lukekarrys)
61d5771 #7541 remove json.stringify from all commands (#7541) (@lukekarrys)
4dfc7d2 #7540 pass strings to JSON.stringify in --json mode (#7540) (@lukekarrys)
3cefdf6 #7538 outdated: return array for outdated deps from multiple workspaces (@lukekarrys)
ef4c975 #7508 view: dont immediately exit on first workspace 404 (#7508) (@lukekarrys)

This PR was generated with Release Please. See documentation.

May 16 '24 02:05 github-actions[bot]

Release Manager

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

Release Checklist for v10.8.1

[ ] 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 7536 --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.1 --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

May 16 '24 02:05 github-actions[bot]

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