chore(deps): update pnpm to v9.15.9 [skip ci] (!1584) · Merge requests · config / eslint-config

This MR contains the following updates:

Package	Change	Age	Confidence
pnpm (source)	`9.6.0` -> `9.15.9`

Release Notes

pnpm/pnpm (pnpm)

`v9.15.9`: pnpm 9.15.9

Compare Source

Patch Changes

Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #8971.

Platinum Sponsors

Gold Sponsors

`v9.15.8`: pnpm 9.15.8

Compare Source

Patch Changes

pnpm self-update should always update the version in the packageManager field of package.json.
The pnpm CLI process should not stay hanging, when --silent reporting is used.
When --loglevel is set to error, don't show installation summary, execution time, and big tarball download progress.
Don't show info output when --loglevel=error is used.

Platinum Sponsors

Gold Sponsors

`v9.15.7`: pnpm 9.15.7

Compare Source

Patch Changes

pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
Allow scope registry CLI option without --config. prefix such as --@scope:registry=https://scope.example.com/npm #9089.
pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
pnpm update -i should list only packages that have newer versions #9206.
Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #9112

Platinum Sponsors

Gold Sponsors

`v9.15.6`: pnpm 9.15.6

Compare Source

Patch Changes

Fix instruction for updating pnpm with corepack #9101.
Print pnpm's version after the execution time at the end of the console output.
The pnpm version specified by packageManager cannot start with v.
Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #8639
Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #8638.

`v9.15.5`: pnpm 9.15.5

Compare Source

Patch Changes

Verify that the package name is valid when executing the publish command.
When running pnpm install, the preprepare and postprepare scripts of the project should be executed #8989.
Quote args for scripts with shell-quote to support new lines (on POSIX only) #8980.
Proxy settings should be respected, when resolving Git-hosted dependencies #6530.
Replace strip-ansi with the built-in util.stripVTControlCharacters #9009.

Platinum Sponsors

Gold Sponsors

`v9.15.4`: pnpm 9.15.4

Compare Source

Patch Changes

Ensure that recursive pnpm update --latest <pkg> updates only the specified package, with dedupe-peer-dependents=true.

Platinum Sponsors

Gold Sponsors

`v9.15.3`: pnpm 9.15.3

Compare Source

Patch Changes

Fixed the Regex used to find the package manifest during packing #8938.
pnpm update --filter <pattern> --latest <pkg> should only change the specified package for the specified workspace, when dedupe-peer-dependents is set to true #8877.
Exclude .DS_Store file at patch-commit #8922.
Fix a bug in which pnpm patch is unable to bring back old patch without specifying @version suffix #8919.

Platinum Sponsors

Gold Sponsors

`v9.15.2`: pnpm 9.15.2

Compare Source

Patch Changes

Fixed publish/pack error with workspace dependencies with relative paths #8904. It was broken in v9.4.0 (398472c).
Use double quotes in the command suggestion by pnpm patch on Windows #7546.
Do not fall back to SSH, when resolving a git-hosted package if git ls-remote works via HTTPS #8906.
Improve how packages with blocked lifecycle scripts are reported during installation. Always print the list of ignored scripts at the end of the output. Include a hint about how to allow the execution of those packages.

Platinum Sponsors

Gold Sponsors

`v9.15.1`: pnpm 9.15.1

Compare Source

Patch Changes

pnpm remove should not link dependencies from the workspace, when link-workspace-packages is set to false #7674.
Installation with hoisted node_modules should not fail, when a dependency has itself in its own peer dependencies #8854.

Platinum Sponsors

Gold Sponsors

`v9.15.0`: pnpm 9.15

Compare Source

Minor Changes

Metadata directory version bumped to force fresh cache after we shipped a fix to the metadata write function. This change is backward compatible as install doesn't require a metadata cache.

Patch Changes

pnpm update --global should not crash if there are no any global packages installed #7898.
Fix an exception when running pnpm update --interactive if catalogs are used.

Platinum Sponsors

Gold Sponsors

`v9.14.4`: pnpm 9.14.4

Compare Source

Patch Changes

Don't ever save mutated metadata to the metadata cache.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

`v9.14.3`: pnpm 9.14.3

Compare Source

Patch Changes

Some commands should ignore the packageManager field check of package.json #7959.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

`v9.14.2`

Compare Source

Patch Changes

pnpm publish --json should work #8788.

Platinum Sponsors

Gold Sponsors

`v9.14.1`

Compare Source

Minor Changes

Added support for pnpm pack --json to print packed tarball and contents in JSON format #8765.

Patch Changes

pnpm exec should print a meaningful error message when no command is provided #8752.
pnpm setup should remove the CLI from the target location before moving the new binary #8173.
Fix ERR_PNPM_TARBALL_EXTRACT error while installing a dependency from GitHub having a slash in branch name #7697.
Don't crash if the use-node-version setting is used and the system has no Node.js installed #8769.
Convert settings in local .npmrc files to their correct types. For instance, child-concurrency should be a number, not a string #5075.
pnpm should fail if a project requires a different package manager even if manage-package-manager-versions is set to true.
pnpm init should respect the --dir option #8768.

Platinum Sponsors

Gold Sponsors

`v9.14.0`

Compare Source

`v9.13.2`: pnpm 9.13.2

Compare Source

Patch Changes

Detection of circular peer dependencies should not crash with aliased dependencies #8759. Fixes a regression introduced in the previous version.
Fix race condition of symlink creations caused by multiple parallel dlx processes.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

`v9.13.1`: pnpm 9.13.1

Compare Source

Patch Changes

Fixed some edge cases where resolving circular peer dependencies caused a dead lock #8720.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

`v9.13.0`: pnpm 9.13

Compare Source

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

Silver Sponsors

`v9.12.3`

Compare Source

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
Fixed an issue in which pnpm deploy --prod fails due to missing devDependencies #8778.

`v9.12.2`

Compare Source

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.

`v9.12.1`

Compare Source

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.

`v9.12.0`

Compare Source

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": {
      "lodash": "-"
    }
  }
}
```

Patch Changes

Fixed an issue where pnpm list --json pkg showed "private": false for a private package #8519.
Packages with libc that differ from pnpm.supportedArchitectures.libc are not downloaded #7362.
Prevent ENOENT errors caused by running store prune in parallel #8586.
Add issues alias to pnpm bugs #8596.

`v9.11.0`

Compare Source

Minor Changes

Experimental: added pnpm cache commands for inspecting the metadata cache #8512.

Patch Changes

Fix a regression in which pnpm deploy with node-linker=hoisted produces an empty node_modules directory #6682.
Don't print a warning when linking packages globally #4761.
pnpm deploy should work in workspace with shared-workspace-lockfile=false #8475.

`v9.10.0`

Compare Source

Minor Changes

Support for a new CLI flag, --exclude-peers, added to the list and why commands. When --exclude-peers is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.

Added a new setting to package.json at pnpm.auditConfig.ignoreGhsas for ignoring vulnerabilities by their GHSA code #6838.

For instance:

{
  "pnpm": {
    "auditConfig": {
      "ignoreGhsas": [
        "GHSA-42xw-2xvc-qx8m",
        "GHSA-4w2v-q235-vp99",
        "GHSA-cph5-m8f7-6c5x",
        "GHSA-vh95-rmgr-6w4m"
      ]
    }
  }
}

Patch Changes

Throw an exception if pnpm switches to the same version of itself.
Reduce memory usage during peer dependencies resolution.

`v9.9.0`

Compare Source

Minor Changes

Minor breaking change. This change might result in resolving your peer dependencies slightly differently but we don't expect it to introduce issues.

We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.

When a peer dependency is a prod dependency somewhere in the dependency graph (with the same version), pnpm will resolve the peers of that peer dependency in the same way across the subgraph.

For example, we have react-dom in the peer deps of the form and button packages. card has react-dom and react as regular dependencies and card is a dependency of form.

These are the direct dependencies of our example project:
```
form
react@16
react-dom@16
```
These are the dependencies of card:
```
button
react@17
react-dom@16
```
When resolving peers, pnpm will not re-resolve react-dom for card, even though card shadows react@16 from the root with react@17. So, all 3 packages (form, card, and button) will use react-dom@16, which in turn uses react@16. form will use react@16, while card and button will use react@17.

Before this optimization react-dom@16 was duplicated for the card, so that card and button would use a react-dom@16 instance that uses react@17.

Before the change:
```
form
-> react-dom@16(react@16)
-> react@16
card
-> react-dom@16(react@17)
-> react@17
button
-> react-dom@16(react@17)
-> react@17
```
After the change
```
form
-> react-dom@16(react@16)
-> react@16
card
-> react-dom@16(react@16)
-> react@17
button
-> react-dom@16(react@16)
-> react@17
```

Patch Changes

pnpm deploy should write the node_modules/.modules.yaml to the node_modules directory within the deploy directory #7731.
Don't override a symlink in node_modules if it already points to the right location pnpm/symlink-dir#54.

`v9.8.0`

Compare Source

Minor Changes

Added a new command for upgrading pnpm itself when it isn't managed by Corepack: pnpm self-update. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #8424.

When executed in a project that has a packageManager field in its package.json file, pnpm will update its version in the packageManager field.

Patch Changes

CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and use-node-version is set.
pnpm setup should never switch to another version of pnpm.

This fixes installation with the standalone script from a directory that has a package.json with the packageManager field. pnpm was installing the version of pnpm specified in the packageManager field due to this issue.
Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #8431.
Remember the state of edit dir, allow running pnpm patch-commit the second time without having to re-run pnpm patch.

`v9.7.1`

Compare Source

Patch Changes

Fixed passing public-hoist-pattern and hoist-pattern via env variables #8339.
pnpm setup no longer creates Batch/Powershell scripts on Linux and macOS #8418.
When dlx uses cache, use the real directory path not the symlink to the cache #8421.
pnpm exec now supports executionEnv #8356.
Remove warnings for non-root pnpm field, add warnings for non-root pnpm subfields that aren't executionEnv #8143.
Replace semver in "peerDependency" with workspace protocol #8355.
Fix a bug in patch-commit in which relative path is rejected #8405.
Update Node.js in @pnpm/exe to v20.

`v9.7.0`

Compare Source

Minor Changes

Added pnpm version management to pnpm. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #8363. This is the same field used by Corepack. Example:
```
{
  "packageManager": "pnpm@9.3.0"
}
```
Added the ability to apply patch to all versions: If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If it is a package name and an exact version (e.g. pkg@x.y.z), pnpm will attempt to apply the patch to that exact version only. Failures will cause pnpm to fail.

If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

If there are multiple versions of pkg installed, pnpm patch pkg will ask which version to edit and whether to attempt to apply the patch to all. If the user chooses to apply the patch to all, pnpm patch-commit $edit_dir would create a pkg entry in pnpm.patchedDependencies. If the user chooses not to apply the patch to all, pnpm patch-commit $edit_dir would create a pkg@x.y.z entry in pnpm.patchedDependencies with x.y.z being the version the user chose to edit.

If the user runs pnpm patch pkg@x.y.z with x.y.z being the exact version of pkg that has been installed, pnpm patch-commit $edit_dir will always create a pkg@x.y.z entry in pnpm.patchedDependencies.
Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[@version] to allow the code editor to open the edit dir in the same file tree as the main project.
Substitute environment variables in config keys #6679.

Patch Changes

pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project doesn't have an install script #8293.
Print warnings to stderr #8342.
Peer dependencies of optional peer dependencies should be automatically installed #8323.

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

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

If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited Jul 29, 2025 by Cenk Kılıç

chore(deps): update pnpm to v9.15.9 [skip ci]

Release Notes

v9.15.9: pnpm 9.15.9

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.8: pnpm 9.15.8

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.7: pnpm 9.15.7

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.6: pnpm 9.15.6

Patch Changes

v9.15.5: pnpm 9.15.5

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.4: pnpm 9.15.4

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.3: pnpm 9.15.3

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.2: pnpm 9.15.2

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.1: pnpm 9.15.1

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.15.0: pnpm 9.15

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.14.4: pnpm 9.14.4

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v9.14.3: pnpm 9.14.3

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

Patch Changes

Platinum Sponsors

Gold Sponsors

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

v9.13.2: pnpm 9.13.2

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v9.13.1: pnpm 9.13.1

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

v9.13.0: pnpm 9.13

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

Silver Sponsors

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

`v9.15.9`: pnpm 9.15.9

`v9.15.8`: pnpm 9.15.8

`v9.15.7`: pnpm 9.15.7

`v9.15.6`: pnpm 9.15.6

`v9.15.5`: pnpm 9.15.5

`v9.15.4`: pnpm 9.15.4

`v9.15.3`: pnpm 9.15.3

`v9.15.2`: pnpm 9.15.2

`v9.15.1`: pnpm 9.15.1

`v9.15.0`: pnpm 9.15

`v9.14.4`: pnpm 9.14.4

`v9.14.3`: pnpm 9.14.3

`v9.13.2`: pnpm 9.13.2

`v9.13.1`: pnpm 9.13.1

`v9.13.0`: pnpm 9.13