chore(deps): update pnpm to v9.15.9 #34
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot]
.This notice will be removed on 2025-10-07.
This PR contains the following updates:
9.12.3+sha512.cce0f9de9c5a7c95bef944169cc5dfe8741abfb145078c0d508b868056848a87c81e626246cb60967cbd7fd29a6c062ef73ff840d96b3c86c40ac92cf4a813ee
->9.15.9
Release Notes
pnpm/pnpm (pnpm)
v9.15.9
: pnpm 9.15.9Compare Source
Patch Changes
Platinum Sponsors
Gold Sponsors
v9.15.8
: pnpm 9.15.8Compare Source
Patch Changes
pnpm self-update
should always update the version in thepackageManager
field ofpackage.json
.--silent
reporting is used.--loglevel
is set toerror
, don't show installation summary, execution time, and big tarball download progress.--loglevel=error
is used.Platinum Sponsors
Gold Sponsors
v9.15.7
: pnpm 9.15.7Compare Source
Patch Changes
pnpm self-update
should not leave a directory with a broken pnpm installation if the installation fails.--config.
prefix such as--@​scope:registry=https://scope.example.com/npm
#9089.pnpm self-update
should not read the pnpm settings from thepackage.json
file in the current working directory.pnpm update -i
should list only packages that have newer versions #9206.catalogs
section of thepnpm-lock.yaml
file to be removed whendedupe-peer-dependents=false
on a filtered install. #9112Platinum Sponsors
Gold Sponsors
v9.15.6
: pnpm 9.15.6Compare Source
Patch Changes
packageManager
cannot start withv
.pnpm-lock.yaml
file when using--fix-lockfile
and--filter
. #8639v9.15.5
: pnpm 9.15.5Compare Source
Patch Changes
pnpm install
, thepreprepare
andpostprepare
scripts of the project should be executed #8989.strip-ansi
with the built-inutil.stripVTControlCharacters
#9009.Platinum Sponsors
Gold Sponsors
v9.15.4
: pnpm 9.15.4Compare Source
Patch Changes
pnpm update --latest <pkg>
updates only the specified package, withdedupe-peer-dependents=true
.Platinum Sponsors
Gold Sponsors
v9.15.3
: pnpm 9.15.3Compare Source
Patch Changes
pnpm update --filter <pattern> --latest <pkg>
should only change the specified package for the specified workspace, whendedupe-peer-dependents
is set totrue
#8877..DS_Store
file atpatch-commit
#8922.pnpm patch
is unable to bring back old patch without specifying@version
suffix #8919.Platinum Sponsors
Gold Sponsors
v9.15.2
: pnpm 9.15.2Compare Source
Patch Changes
publish
/pack
error with workspace dependencies with relative paths #8904. It was broken inv9.4.0
(398472c).pnpm patch
on Windows #7546.git ls-remote
works via HTTPS #8906.Platinum Sponsors
Gold Sponsors
v9.15.1
: pnpm 9.15.1Compare Source
Patch Changes
pnpm remove
should not link dependencies from the workspace, whenlink-workspace-packages
is set tofalse
#7674.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.15Compare Source
Minor Changes
Patch Changes
pnpm update --global
should not crash if there are no any global packages installed #7898.pnpm update --interactive
if catalogs are used.Platinum Sponsors
Gold Sponsors
v9.14.4
: pnpm 9.14.4Compare Source
Patch Changes
Platinum Sponsors
Gold Sponsors
Silver Sponsors