chore(deps): update pnpm to v10.33.0
This MR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| pnpm (source) | 10.30.1 → 10.33.0 |
Release Notes
pnpm/pnpm (pnpm)
v10.33.0: pnpm 10.33
Minor Changes
- Added a new
dedupePeerssetting that reduces peer dependency duplication. When enabled, peer dependency suffixes use version-only identifiers (name@version) instead of full dep paths, eliminating nested suffixes like(foo@1.0.0(bar@2.0.0)). This dramatically reduces the number of package instances in projects with many recursive peer dependencies #11070.
Patch Changes
-
Fail on incompatible lockfiles in CI when frozen lockfile mode is enabled, while preserving non-frozen CI fallback behavior.
-
When package metadata is malformed or can't be fetched, the error thrown will now show the originating error.
-
Fixed intermittent failures when multiple
pnpm dlxcalls run concurrently for the same package. When the global virtual store is enabled, the importer now verifies file content before skipping a rename, avoiding destructive swap-renames that break concurrent processes. Also tolerates EPERM during bin creation on Windows and properly propagatesenableGlobalVirtualStorethrough the install pipeline. -
Fixed handling of non-string version selectors in
hoistPeers, preventing invalid peer dependency specifiers. -
Improve the non-interactive modules purge error hint to include the
confirmModulesPurge=falseworkaround.When pnpm needs to recreate
node_modulesbut no TTY is available, the error now suggests either settingCI=trueor disabling the purge confirmation prompt viaconfirmModulesPurge=false.Adds a regression test for the non-TTY flow.
-
Fixed false "Command not found" errors on Windows when a command exists in PATH but exits with a non-zero code. Also fixed path resolution for
--filtercontexts where the command runs in a different package directory. -
When a pnpm-lock.yaml contains two documents, ignore the first one. pnpm v11 will write two lockfile documents into pnpm-lock.yaml in order to store pnpm version integrities and config dependency resolutions.
-
Fixed a bug preventing the
clearCachefunction returned bycreateNpmResolverfrom properly clearing metadata cache.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
|
|
|
v10.32.1: pnpm 10.32.1
Patch Changes
- Fix a regression where
pnpm-workspace.yamlwithout apackagesfield caused all directories to be treated as workspace projects. This broke projects that usepnpm-workspace.yamlonly for settings (e.g.minimumReleaseAge) without defining workspace packages #10909.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
|
|
|
v10.32.0: pnpm 10.32
Minor Changes
- Added
--allflag topnpm approve-buildsthat approves all pending builds without interactive prompts #10136.
Patch Changes
- Reverted change related to setting explicitly the npm config file path, which caused regressions.
- Reverted fix related to
lockfile-include-tarball-url. Fixes #10915.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
|
|
|
v10.31.0: pnpm 10.31
Minor Changes
- When pnpm updates the
pnpm-workspace.yaml, comments, string formatting, and whitespace will be preserved.
Patch Changes
-
Added
-Fas a short alias for the--filteroption in the help output. -
Handle undefined pkgSnapshot in
pnpm why -r#10700. -
Fix headless install not being used when a project has an injected self-referencing
file:dependency that resolves tolink:in the lockfile. -
Fixed a race condition when multiple worker threads import the same package to the global virtual store concurrently. The rename operation now tolerates
ENOTEMPTY/EEXISTerrors if another thread already completed the import. -
When
lockfile-include-tarball-urlis set tofalse, tarball URLs are now always excluded from the lockfile. Previously, tarball URLs could still appear for packages hosted under non-standard URLs, making the behavior flaky and inconsistent #6667. -
Fixed
optimisticRepeatInstallskipping install whenoverrides,packageExtensions,ignoredOptionalDependencies,patchedDependencies, orpeersSuffixMaxLengthchanged. -
Fixed
pnpm patch-commitfailing with "unable to access '/.config/git/attributes': Permission denied" error in environments where HOME is unset or non-standard (Docker containers, CI systems).The issue occurred because pnpm was setting
HOMEand the Windows user profile env var to empty strings to suppress user git configuration when runninggit diff. This caused git to resolve the home directory (~) as root (/), leading to permission errors when attempting to access/.config/git/attributes.Now uses
GIT_CONFIG_GLOBAL: os.devNullinstead, which is git's proper mechanism for bypassing user-level configuration without corrupting the home directory path resolution.Fixes #6537
-
Fix
pnpm why -r --parseablemissing dependents when multiple workspace packages share the same dependency #8100. -
Fix
link-workspace-packages=trueincorrectly linking workspace packages when the requested version doesn't match the workspace package's version. Previously, on fresh installs the version constraint is overridden to*in the fallback resolution paths, causing any workspace package with a matching name to be linked regardless of version #10173. -
Fixed
pnpm update --interactivetable breaking with long version strings (e.g., prerelease versions like7.0.0-dev.20251209.1) by dynamically calculating column widths instead of using hardcoded values #10316. -
Explicitly tell
npmthe path to the globalrcconfig file. -
The parameter set by the
--allow-buildflag is written toallowBuilds. -
Fix a bug in which specifying
filteronpnpm-workspace.yamlwould cause pnpm to not detect any projects. -
Print help message on running pnpm dlx without arguments and exit.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
|
|
|
v10.30.3: pnpm 10.30.3
Patch Changes
- Fixed version switching via
packageManagerfield failing when pnpm is installed as a standalone executable in environments without a system Node.js #10687.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
|
|
|
v10.30.2: pnpm 10.30.2
Patch Changes
- Fix auto-installed peer dependencies ignoring overrides when a stale version exists in the lockfile.
- Fixed "input line too long" error on Windows when running lifecycle scripts with the global virtual store enabled #10673.
- Update @zkochan/js-yaml to fix moderate vulnerability.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
|
|
|
Configuration
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
- If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.