chore(deps): update dependency pnpm to v9.15.9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pnpm (source)	9 -> 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

	Mend Renovate. View the repository job log.

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 1 hour (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 14 hours (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 7 hours (more than 100, code: "api-deployments-free-per-day").

[netlify]

❌ Deploy Preview for safe-vault failed. Why did it fail? →

Name	Link
🔨 Latest commit	f213eb8
🔍 Latest deploy log	https://app.netlify.com/projects/safe-vault/deploys/68abb516d156be0008dc3726

[netlify]

❌ Deploy Preview for safe-vaultt failed. Why did it fail? →

Name	Link
🔨 Latest commit	f213eb8
🔍 Latest deploy log	https://app.netlify.com/projects/safe-vaultt/deploys/68abb5163fed920008411045

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
gnosis	Error			Aug 25, 2025 1:00am
gnosispro	Error			Aug 25, 2025 1:00am
safe	Error			Aug 25, 2025 1:00am
safe-app	Error			Aug 25, 2025 1:00am
safe-vault	Error			Aug 25, 2025 1:00am
safe-vault-f44t	Error			Aug 25, 2025 1:00am
safe-vault-pro	Error			Aug 25, 2025 1:00am
safe-vault-xm9a	Error			Aug 25, 2025 1:00am
safe-vault3	Error			Aug 25, 2025 1:00am

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 10 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/safewallet-pros-projects?upgradeToPro=build-rate-limit

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 4 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/safewallet-pros-projects?upgradeToPro=build-rate-limit

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 12 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/safewallet-pros-projects?upgradeToPro=build-rate-limit

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gnosis-vaults-projects?upgradeToPro=build-rate-limit

[vercel]

Deployment failed with the following error:

Too many requests - try again in 1 minute (more than 60, code: "api-deployments-flood").

Learn More: https://vercel.com/docs/limits#rate-limits

[vercel]

Deployment failed with the following error:

Too many requests - try again in 56 seconds (more than 60, code: "api-deployments-flood").

Learn More: https://vercel.com/docs/limits#rate-limits

[vercel]

Deployment failed with the following error:

Too many requests - try again in 54 seconds (more than 60, code: "api-deployments-flood").

Learn More: https://vercel.com/docs/limits#rate-limits

[vercel]

Deployment failed with the following error:

Too many requests - try again in 55 seconds (more than 60, code: "api-deployments-flood").

Learn More: https://vercel.com/docs/limits#rate-limits

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 1 hour (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/gnosis-vaults-projects?upgradeToPro=build-rate-limit