chore: release 9.0.0-pre.3

[github-actions]

🤖 I have created a release beep boop

9.0.0-pre.3

9.0.0-pre.3 (2022-09-30)

⚠️ BREAKING CHANGES

• npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.
• --timing file changes:
  • When run with the --timing flag, npm now writes timing data to a
    file alongside the debug log data, respecting the logs-dir option and
    falling back to <CACHE>/_logs/ dir, instead of directly inside the
    cache directory.
  • The timing file data is no longer newline delimited JSON, and instead
    each run will create a uniquely named <ID>-timing.json file, with the
    <ID> portion being the same as the debug log.
  • Finally, the data inside the file now has three top level keys,
    metadata, timers, and unfinishedTimers` instead of everything being
    a top level key.

Features

• 3ae796d implement new npm-packlist behavior (@lukekarrys)
• e64d69a #5581 write eresolve error files to the logs directory (@lukekarrys)
• 3445da0 timings are now written alongside debug log files (@lukekarrys)

Documentation

• f0e7584 #5601 update docs/logging for new --access default (@wraithgar)

Dependencies

• bc21552 #5603 [email protected]
• Workspace: @npmcli/[email protected]
• Workspace: [email protected]
• Workspace: [email protected]
• Workspace: [email protected]
• Workspace: [email protected]
• Workspace: [email protected]

arborist: 6.0.0-pre.3

6.0.0-pre.3 (2022-09-30)

⚠️ BREAKING CHANGES

• npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.

Features

• 3ae796d implement new npm-packlist behavior (@lukekarrys)

libnpmdiff: 5.0.0-pre.1

5.0.0-pre.1 (2022-09-30)

⚠️ BREAKING CHANGES

• npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.

Features

• 3ae796d implement new npm-packlist behavior (@lukekarrys)

Dependencies

• Workspace: @npmcli/[email protected]

libnpmexec: 5.0.0-pre.3

5.0.0-pre.3 (2022-09-30)

⚠️ BREAKING CHANGES

• npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.

Features

• 3ae796d implement new npm-packlist behavior (@lukekarrys)

Dependencies

• Workspace: @npmcli/[email protected]

libnpmfund: 4.0.0-pre.3

4.0.0-pre.3 (2022-09-30)

Dependencies

• Workspace: @npmcli/[email protected]

libnpmpack: 5.0.0-pre.1

5.0.0-pre.1 (2022-09-30)

⚠️ BREAKING CHANGES

• npm pack now follows a strict order of operations when applying ignore rules. If a files array is present in the package.json, then rules in .gitignore and .npmignore files from the root will be ignored.

Features

• 3ae796d implement new npm-packlist behavior (@lukekarrys)

Dependencies

• Workspace: @npmcli/[email protected]

libnpmpublish: 7.0.0-pre.1

7.0.0-pre.1 (2022-09-30)

⚠️ BREAKING CHANGES

• The default value of access is now public

Features

• 525654e default access to public (@wraithgar)

Documentation

• f0e7584 #5601 update docs/logging for new --access default (@wraithgar)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Release Manager

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

Release Checklist for v9.0.0-pre.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 5589 --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 @npmcli/arborist --tag prerelease
  node . publish -w libnpmdiff --tag prerelease
  node . publish -w libnpmexec --tag prerelease
  node . publish -w libnpmfund --tag prerelease
  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 resetdepts

• 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.3!
  
  https://github.com/npm/cli/releases/tag/v9.0.0-pre.3
  
  Release details...
  

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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

[github-actions]

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