chore(deps): bump pnpm from 9.11.0 to 9.13.0

[dependabot]

Bumps pnpm from 9.11.0 to 9.13.0.

Release notes

Sourced from pnpm's releases.

pnpm 9.13

Minor Changes

• The self-update now accepts a version specifier to install a specific version of pnpm. E.g.:

  pnpm self-update 9.5.0
  

  or

  pnpm self-update next-10
  

Patch Changes

• Fix Cannot read properties of undefined (reading 'name') that is printed while trying to render the missing peer dependencies warning message #8538.

Platinum Sponsors

Gold Sponsors

... (truncated)

Changelog

Sourced from pnpm's changelog.

9.13.0

Minor Changes

• The self-update now accepts a version specifier to install a specific version of pnpm. E.g.: pnpm self-update 9.5.0 or pnpm self-update next-10.

Patch Changes

• Fix Cannot read properties of undefined (reading 'name') that is printed while trying to render the missing peer dependencies warning message #8538.

9.12.3

Patch Changes

• Don't purge node_modules, when typing "n" in the prompt that asks whether to remove node_modules before installation #8655.
• Fix a bug causing pnpm to infinitely spawn itself when manage-package-manager-versions=true is set and the .tools directory is corrupt.
• Use crypto.hash, when available, for improved performance #8629.
• Fixed a race condition in temporary file creation in the store by including worker thread ID in filename. Previously, multiple worker threads could attempt to use the same temporary file. Temporary files now include both process ID and thread ID for uniqueness #8703.
• All commands should read settings from the package.json at the root of the workspace #8667.
• When manage-package-manager-versions is set to true, errors spawning a self-managed version of pnpm will now be shown (instead of being silent).
• Pass the find command to npm, it is an alias for npm search

9.12.2

Patch Changes

• When checking whether a file in the store has executable permissions, the new approach checks if at least one of the executable bits (owner, group, and others) is set to 1. Previously, a file was incorrectly considered executable only when all the executable bits were set to 1. This fix ensures that files with any executable permission, regardless of the user class, are now correctly identified as executable #8546.

9.12.1

Patch Changes

• pnpm update --latest should not update the automatically installed peer dependencies #6657.
• pnpm publish should be able to publish from a local tarball #7950.
• The pnpx command should work correctly on Windows, when pnpm is installed via the standalone installation script #8608.
• Prevent EBUSY errors caused by creating symlinks in parallel dlx processes #8604.
• Fix maximum call stack size exceeded error related to circular workspace dependencies #8599.

9.12.0

Minor Changes

• Fix peer dependency resolution dead lock #8570. This change might change some of the keys in the snapshots field inside pnpm-lock.yaml but it should happen very rarely.

• pnpm outdated command supports now a --sort-by=name option for sorting outdated dependencies by package name #8523.

• Added the ability for overrides to remove dependencies by specifying "-" as the field value #8572. For example, to remove lodash from the dependencies, use this configuration in package.json:

  {
    "pnpm": {
      "overrides": {

... (truncated)

Commits

• d9988f1 chore(release): 9.13.0
• 81fa780 fix: rendering of missing peer dependencies output (#8745)
• af5d297 docs: improve the image tags (#8721)
• 0309365 chore(release): 9.12.3
• 1dd419c test: fix killing the registry mock server on teardown (#8695)
• 2aed76d fix: fork bomb when pnpm self-manages its version (#8679)
• 74b6f73 chore: fix esbuild external warning (#8692)
• 016c58b chore: fix pd for local development (#8691)
• 78412f2 fix(pnpm): change printError to write to stderr instead of stdout (#8662)
• 45c0c6d chore: add "directory" to package.json "repository" (#8672)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Great job, @dependabot[bot]! 🎉 Thank you for submitting your first pull request. Your contribution is valuable and we appreciate your efforts to improve our project.

We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines

[dependabot]

Superseded by #2642.