chore: release 9.0.0-pre.5

[github-actions]

🤖 I have created a release beep boop

9.0.0-pre.5

9.0.0-pre.5 (2022-10-13)

⚠️ BREAKING CHANGES

• the presence of auth related settings that are not scoped to a specific registry found in a config file is no longer supported and will throw errors
• the node-version and npm-version configs have been removed.
• links generated from git urls will now use HEAD instead of master as the default ref

Features

• a09e19d #5696 introduce the npm config fix command (@nlf)
• d2963c6 explicitly validate config within the cli (@nlf)
• a5fec08 rewrite docs generation (@lukekarrys)

Bug Fixes

• a35c784 #5691 config: remove node-version and npm-version (@wraithgar)

Documentation

• a8532eb #5661 typo missing parentheses (@hbrls)
• 542efdb update folders page for modern npm (@shalvah)

Dependencies

• cee3fd9 @npmcli/[email protected]
• 2a740b1 #5692 [email protected]
• Workspace: [email protected]
• Workspace: [email protected]

libnpmpack: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-13)

Bug Fixes

• a990c3c #5651 libnpmpack: obey ignoreScripts (@winterqt)

libnpmpublish: 7.0.0-pre.3

7.0.0-pre.3 (2022-10-13)

Dependencies

• Workspace: [email protected]

---

This PR was generated with Release Please. See documentation.

[github-actions]

Release Manager

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

Release Checklist for v9.0.0-pre.5

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

• 2. Run tests locally

  These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

  node . run lint-all
  node . run test-all
  node scripts/git-dirty.js

• 3. Check CI status

  gh pr checks --watch

• 4. Publish workspaces

  Note:
  If we are currently publishing prereleases, make sure to publish with the prerelease tag.

  node . publish -w libnpmpack --tag prerelease
  node . publish -w libnpmpublish --tag prerelease

• 5. Publish the CLI

  Note:
  This will publish with the dist-tag set to next-9

  make publish

• 6. Merge release PR

  gh pr merge --rebase
  git checkout latest
  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.0.0-pre.5!
  
  https://github.com/npm/cli/releases/tag/v9.0.0-pre.5
  
  Release details...
  

[github-actions]

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.5 🌻

[github-actions]

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

[github-actions]

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