chore: release 9.1.3

[github-actions]

🤖 I have created a release beep boop

9.1.3

9.1.3 (2022-11-30)

Bug Fixes

• ffbdea2 #5894 npm pack filename on scoped packages (fix: npm pack filename on scoped packages #5894) (@HenryNguyen5)
• c26d708 #5884 validate username at get-identity (fix: Validate username at get-identity #5884) (@sosoba, @nlf)

Documentation

• ea948dc #5881 update description of npm exec (docs: update description of npm exec #5881) (@styfle, @wraithgar)
• 40f2c21 #5865 ci-info url (docs: ci-info url #5865) (@wraithgar)
• 681a45b #5875 run the comand for directory workspaces (docs: add workspace directory example #5875) (@1aron)
• 681a45b #5875 add workspace directory example (docs: add workspace directory example #5875) (@1aron)

Dependencies

• Workspace: @npmcli/arborist@6.1.4
• Workspace: libnpmdiff@5.0.5
• Workspace: libnpmexec@5.0.5
• Workspace: libnpmfund@4.0.5
• Workspace: libnpmpack@5.0.5
• Workspace: libnpmpublish@7.0.5

arborist: 6.1.4

6.1.4 (2022-11-30)

Bug Fixes

• 80c6c4a #5907 do not reset hidden lockfile data before saving (fix: do not reset hidden lockfile data before saving #5907) (@nlf)

libnpmdiff: 5.0.5

5.0.5 (2022-11-30)

Dependencies

• Workspace: @npmcli/arborist@6.1.4

libnpmexec: 5.0.5

5.0.5 (2022-11-30)

Dependencies

• Workspace: @npmcli/arborist@6.1.4

libnpmfund: 4.0.5

4.0.5 (2022-11-30)

Dependencies

• Workspace: @npmcli/arborist@6.1.4

libnpmpack: 5.0.5

5.0.5 (2022-11-30)

Dependencies

• Workspace: @npmcli/arborist@6.1.4

libnpmpublish: 7.0.5

7.0.5 (2022-11-30)

Dependencies

• Workspace: libnpmpack@5.0.5

---

This PR was generated with Release Please. See documentation.

[github-actions]

Release Manager

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

Force CI to Update This Release

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

gh workflow run release.yml -r latest 

Release Checklist for v9.1.3

• 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 5912 --force node . run resetdeps node scripts/git-dirty.js

• 2. Check CI status

  gh pr checks --watch

• 3. Publish the CLI

  Warning:
  This will publish all updated workspaces, 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.1.3 locally

  npm i -g npm@9.1.3 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.1.3 latest

• 6. Merge release PR

  gh pr merge --rebase git checkout latest git fetch git reset --hard origin/latest node . run resetdeps

• 7. Check For Release Tags

  Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

  gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"` 

• 8. Post on Twitter

  New @npmjs release: 9.1.3! https://github.com/npm/cli/releases/tag/v9.1.3 Release details... 

• 9. Trigger docs.npmjs.com update

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

• 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.

  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.

  gh repo sync npm/node --source nodejs/node --force 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).

  # This will create a PR on nodejs/node to the `v18.x-staging` branch gh workflow run create-node-pr.yml -f spec=next-9 -f branch=18

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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