-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update pnpm to v9.15.9 #395
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
dd12c25
to
2ff47cd
Compare
2ff47cd
to
5a0bc1d
Compare
5a0bc1d
to
b48190a
Compare
b48190a
to
8afff6d
Compare
8afff6d
to
6ceeb30
Compare
6ceeb30
to
0aaeea0
Compare
0aaeea0
to
7893456
Compare
cbaf84a
to
c7c870d
Compare
c7c870d
to
644f3aa
Compare
644f3aa
to
b56b2aa
Compare
b56b2aa
to
938c15a
Compare
938c15a
to
b48ae3a
Compare
b48ae3a
to
9243a65
Compare
9243a65
to
cf4b409
Compare
cf4b409
to
484e0ee
Compare
This PR contains the following updates:
9.12.1+sha512.e5a7e52a4183a02d5931057f7a0dbff9d5e9ce3161e33fa68ae392125b79282a8a8a470a51dfc8a0ed86221442eb2fb57019b0990ed24fab519bf0e1bc5ccfc4
->9.15.9
Release Notes
pnpm/pnpm (pnpm)
v9.15.9
Compare Source
v9.15.8
Compare Source
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
v9.14.3
: pnpm 9.14.3Compare Source
Patch Changes
packageManager
field check ofpackage.json
#7959.Platinum Sponsors
Gold Sponsors
Silver Sponsors
v9.14.2
Compare Source
Patch Changes
pnpm publish --json
should work #8788.Platinum Sponsors
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.
This PR was generated by Mend Renovate. View the repository job log.