chore: release 9.9.2

[github-actions]

🤖 I have created a release beep boop

9.9.2

9.9.2 (2023-11-14)

Bug Fixes

• 4c9a5e1 #6993 look in workspace for exec commands (fix: look in workspace for exec commands #6993) (@wraithgar)
• bb6f496 #6992 correctly handle object licenses in SBOM generation (fix: correctly handle object licenses in SBOM generation #6992) (@bdehamer, @jamietanna)
• 10db3ca #6990 pkg: properly output in workspace mode (fix(pkg): properly output in workspace mode (#6977) #6990) (@wraithgar)

Documentation

• 6ab06d7 #6985 update npm-prune description (docs: update npm-prune description #6985) (@Eomm)

Dependencies

• Workspace: libnpmpublish@7.5.1

libnpmpublish: 7.5.1

7.5.1 (2023-11-14)

Bug Fixes

• 68e5cb6 #6991 split github workflow ref (fix: split github workflow ref (v9 backport) #6991) (@bdehamer, @sxzz)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Release Manager

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

Force CI to Update This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to release/v9. To force CI to update this PR, run this command:

gh workflow run release.yml -r release/v9 -R npm/cli -f release-pr=6988

Release Checklist for v9.9.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 6988 --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-9.

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

  npm i -g npm@9.9.2

  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 9 is not being set to latest.

  node . dist-tag add npm@9.9.2 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 release/v9

  git fetch

  git reset --hard origin/release/v9

  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 release/v9 -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 v9.9.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-9

  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-9 -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

[github-actions]

Release Workflow

• npm@9.9.2 https://github.com/npm/cli/releases/tag/v9.9.2
• libnpmpublish@7.5.1 https://github.com/npm/cli/releases/tag/libnpmpublish-v7.5.1
• Workflow run: ❌ https://github.com/npm/cli/actions/runs/6883146828

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