chore(deps): update pnpm to v10.6.0 #312
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "renovate/pnpm-10.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
10.5.2
->10.6.0
10.6.1
Release Notes
pnpm/pnpm (pnpm)
v10.6.0
Compare Source
Minor Changes
pnpm-workspace.yaml
can now hold all the settings that.npmrc
accepts. The settings should use camelCase #9211.pnpm-workspace.yaml
example:Projects using a
file:
dependency on a local tarball file (i.e..tgz
,.tar.gz
,.tar
) will see a performance improvement during installation. Previously, using afile:
dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.Patch Changes
pnpm self-update
should not leave a directory with a broken pnpm installation if the installation fails.fast-glob
replace withtinyglobby
to reduce the size of the pnpm CLI dependencies #9169.pnpm deploy
should not remove fields from the deployed package'spackage.json
file #9215.pnpm self-update
should not read the pnpm settings from thepackage.json
file in the current working directory.pnpm deploy
creating apackage.json
without theimports
andlicense
field #9193.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. #9112Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.