chore(deps): update pnpm to v8.13.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	8.6.12 -> 8.13.1

---

Release Notes

pnpm/pnpm (pnpm)

v8.13.1

Minor Changes

• New commands added for inspecting the store:

  • pnpm cat-index: Prints the index file of a specific package in the store. The package is specified by its name and version: pnpm cat-index <pkg name>@&#8203;<pkg version>
  • pnpm cat-file: Prints the contents of a file based on the hash value stored in the index file. For example:
    pnpm cat-file sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==
  • pnpm find-hash: Lists the packages that include the file with the specified hash. For example:
    pnpm find-hash sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==
    This command is experimental. We might change how it behaves.

  Related issue: #​7413.

• A new setting added for symlinking injected dependencies from the workspace, if their dependencies use the same peer dependencies as the dependent package. The setting is called dedupe-injected-deps #​7416.

• Use --fail-if-no-match if you want the CLI fail if no packages were matched by the command #​7403.

Patch Changes

• pnpm list --parseable should not print the same dependency multiple times #​7429.
• Fix error message texts in the pnpm env commands #​7456.
• Better support for light themed terminals by the pnpm update --interactive command #​7439.
• Fix EPERM error that occasionally happened on Windows during renames in the store #​7213.
• Fix error as in update -i -r with Git specifiers #​7415.
• Added support for boolean values in 'bundleDependencies' package.json fields when installing a dependency. Fix to properly handle 'bundledDependencies' alias #​7411.

Our Gold Sponsors

Our Silver Sponsors

v8.12.1

Compare Source

Patch Changes

• Don't report dependencies with optional dependencies as being added on repeat install. This was a bug in reporting #​7384.
• Fix a bug where --fix-lockfile crashes on tarballs #​7368.
• Do not create empty patch directory.
• Installation should not fail if an empty node_modules directory cannot be removed #​7405.

Our Gold Sponsors

Our Silver Sponsors

v8.12.0

Compare Source

Minor Changes

• Add support for basic authorization header #​7371.

Patch Changes

• Fix a bug where pnpm incorrectly passes a flag to a run handler as a fallback command #​7244.
• When dedupe-direct-deps is set to true, commands of dependencies should be deduplicated #​7359.

Our Gold Sponsors

Our Silver Sponsors

v8.11.0

Compare Source

Minor Changes

• (IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain /<pkg_name>@&#8203;<pkg_version, not <domain>/<pkg_name>@&#8203;<pkg_version>.

  This change is a fix to avoid the same package from being added to node_modules/.pnpm multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.

  We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.

  Related PR: #​7318.

Patch Changes

• pnpm add a-module-already-in-dev-deps will show a message to notice the user that the package was not moved to "dependencies" #​926.
• The modules directory should not be removed if the registry configuration has changed.
• Fix missing auth tokens in registries with paths specified (e.g. //npm.pkg.github.com/pnpm). #​5970 #​2933

Our Gold Sponsors

Our Silver Sponsors

v8.10.5

Compare Source

Patch Changes

• Don't fail on an empty pnpm-workspace.yaml file #​7307.

Our Gold Sponsors

Our Silver Sponsors

v8.10.4

Compare Source

Patch Changes

• Fixed out-of-memory exception that was happening on dependencies with many peer dependencies, when node-linker was set to hoisted #​6227.

Our Gold Sponsors

Our Silver Sponsors

v8.10.3

Compare Source

Patch Changes

• (Important) Increased the default amount of allowed concurrent network request on systems that have more than 16 CPUs #​7285.

• pnpm patch should reuse existing patch when shared-workspace-file=false #​7252.

• Don't retry fetching missing packages, since the retries will never work #​7276.

• When using pnpm store prune --force alien directories are removed from the store #​7272.

• Downgraded npm-packlist because the newer version significantly slows down the installation of local directory dependencies, making it unbearably slow.

  npm-packlist was upgraded in this PR to fix #​6997. We added our own file deduplication to fix the issue of duplicate file entries.

• Fixed a performance regression on running installation on a project with an up to date lockfile #​7297.

• Throw an error on invalid pnpm-workspace.yaml file #​7273.

Our Gold Sponsors

Our Silver Sponsors

v8.10.2

Compare Source

Patch Changes

• Fixed a regression that was shipped with pnpm v8.10.0. Dependencies that were already built should not be rebuilt on repeat install. This issue was introduced via the changes related to supportedArchitectures. Related issue #​7268.

Our Gold Sponsors

Our Silver Sponsors

v8.10.1

Compare Source

Patch Changes

• (Important) Tarball resolutions in pnpm-lock.yaml will no longer contain a registry field. This field has been unused for a long time. This change should not cause any issues besides backward compatible modifications to the lockfile #​7262.
• Fix issue when trying to use pnpm dlx in the root of a Windows Drive #​7263.
• Optional dependencies that do not have to be built will be reflinked (or hardlinked) to the store instead of copied #​7046.
• If a package's tarball cannot be fetched, print the dependency chain that leads to the failed package #​7265.
• After upgrading one of our dependencies, we started to sometimes have an error on publish. We have forked @npmcli/arborist to patch it with a fix #​7269.

Our Gold Sponsors

Our Silver Sponsors

v8.10.0

Compare Source

Minor Changes

• Support for multiple architectures when installing dependencies #​5965.

  You can now specify architectures for which you'd like to install optional dependencies, even if they don't match the architecture of the system running the install. Use the supportedArchitectures field in package.json to define your preferences.

  For example, the following configuration tells pnpm to install optional dependencies for Windows x64:

  {
    "pnpm": {
      "supportedArchitectures": {
        "os": ["win32"],
        "cpu": ["x64"]
      }
    }
  }

  Whereas this configuration will have pnpm install optional dependencies for Windows, macOS, and the architecture of the system currently running the install. It includes artifacts for both x64 and arm64 CPUs:

  {
    "pnpm": {
      "supportedArchitectures": {
        "os": ["win32", "darwin", "current"],
        "cpu": ["x64", "arm64"]
      }
    }
  }

  Additionally, supportedArchitectures also supports specifying the libc of the system.

• The pnpm licenses list command now accepts the --filter option to check the licenses of the dependencies of a subset of workspace projects [#​5806](https://togithub.com/pnpm

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.