chore(deps): update pnpm to v10.12.2 #601

renovate · 2025-06-07T08:40:47Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pnpm (source)	`10.5.1` -> `10.12.2`

Release Notes

pnpm/pnpm (pnpm)

`v10.12.2`

Compare Source

Patch Changes

Fixed hoisting with enableGlobalVirtualStore set to true #9648.
Fix the --help and -h flags not working as expected for the pnpm create command.
The dependency package path output by the pnpm licenses list --json command is incorrect.
Fix a bug in which pnpm deploy fails due to overridden dependencies having peer dependencies causing ERR_PNPM_OUTDATED_LOCKFILE #9595.

`v10.12.1`

Minor Changes

Experimental. Added support for global virtual stores. When enabled, node_modules contains only symlinks to a central virtual store, rather to node_modules/.pnpm. By default, this central store is located at <store-path>/links (you can find the store path by running pnpm store path).

In the central virtual store, each package is hard linked into a directory whose name is the hash of its dependency graph. This allows multiple projects on the system to symlink shared dependencies from this central location, significantly improving installation speed when a warm cache is available.

This is conceptually similar to how NixOS manages packages, using dependency graph hashes to create isolated and reusable package directories.

To enable the global virtual store, set enableGlobalVirtualStore: true in your root pnpm-workspace.yaml, or globally via:
```
pnpm config -g set enable-global-virtual-store true
```
NOTE: In CI environments, where caches are typically cold, this setting may slow down installation. pnpm automatically disables the global virtual store when running in CI.

Related PR: #8190

The pnpm update command now supports updating catalog: protocol dependencies and writes new specifiers to pnpm-workspace.yaml.
Added two new CLI options (--save-catalog and --save-catalog-name=<name>) to pnpm add to save new dependencies as catalog entries. catalog: or catalog:<name> will be added to package.json and the package specifier will be added to the catalogs or catalog[<name>] object in pnpm-workspace.yaml #9425.
Semi-breaking. The keys used for side-effects caches have changed. If you have a side-effects cache generated by a previous version of pnpm, the new version will not use it and will create a new cache instead #9605.
Added a new setting called ci for explicitly telling pnpm if the current environment is a CI or not.

Patch Changes

Sort versions printed by pnpm patch using semantic versioning rules.
Improve the way the error message displays mismatched specifiers. Show differences instead of 2 whole objects #9598.
Revert #9574 to fix a regression #9596.

`v10.11.1`

Compare Source

Patch Changes

Fix an issue in which pnpm deploy --legacy creates unexpected directories when the root package.json has a workspace package as a peer dependency #9550.
Dependencies specified via a URL that redirects will only be locked to the target if it is immutable, fixing a regression when installing from GitHub releases. (#9531)
Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #9505.
Use pnpm_config_ env variables instead of npm_config_ #9571.
Fix a regression (in v10.9.0) causing the --lockfile-only flag on pnpm update to produce a different pnpm-lock.yaml than an update without the flag.
Let pnpm deploy work in repos with overrides when inject-workspace-packages=true #9283.
Fixed the problem of path loss caused by parsing URL address. Fixes a regression shipped in pnpm v10.11 via #9502.
pnpm -r --silent run should not print out section #9563.

`v10.11.0`

Compare Source

Minor Changes

A new setting added for pnpm init to create a package.json with type=module, when init-type is module. Works as a flag for the init command too #9463.
Added support for Nushell to pnpm setup #6476.
Added two new flags to the pnpm audit command, --ignore and --ignore-unfixable #8474.

Ignore all vulnerabilities that have no solution:
```
> pnpm audit --ignore-unfixable
```
Provide a list of CVE's to ignore those specifically, even if they have a resolution.
```
> pnpm audit --ignore=CVE-2021-1234 --ignore=CVE-2021-5678
```
Added support for recursively running pack in every project of a workspace #4351.

Now you can run pnpm -r pack to pack all packages in the workspace.

Patch Changes

pnpm version management should work, when dangerouslyAllowAllBuilds is set to true #9472.
pnpm link should work from inside a workspace #9506.
Set the default workspaceConcurrency to Math.min(os.availableParallelism(), 4) #9493.
Installation should not exit with an error if strictPeerDependencies is true but all issues are ignored by peerDependencyRules #9505.
Read updateConfig from pnpm-workspace.yaml #9500.
Add support for recursive pack
Remove url.parse usage to fix warning on Node.js 24 #9492.
pnpm run should be able to run commands from the workspace root, if ignoreScripts is set tot true #4858.

`v10.10.0`

Compare Source

Minor Changes

Allow loading the preResolution, importPackage, and fetchers hooks from local pnpmfile.

Patch Changes

Fix cd command, when shellEmulator is true #7838.
Sort keys in pnpm-workspace.yaml #9453.
Pass the npm_package_json environment variable to the executed scripts #9452.
Fixed a mistake in the description of the --reporter=silent option.

`v10.9.0`

Compare Source

Minor Changes

Added support for installing JSR packages. You can now install JSR packages using the following syntax:
```
pnpm add jsr:<pkg_name>
```
or with a version range:
```
pnpm add jsr:<pkg_name>@&#8203;<range>
```
For example, running:
```
pnpm add jsr:@&#8203;foo/bar
```
will add the following entry to your package.json:
```
{
  "dependencies": {
    "@&#8203;foo/bar": "jsr:^0.1.2"
  }
}
```
When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:
```
{
  "dependencies": {
    "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
  }
}
```
Related issue: #8941.

Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.
Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:
```
neverBuiltDependencies: []
```
dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:
```
pnpm config set dangerouslyAllowAllBuilds true
```
It can also be set when running a command:
```
pnpm install --dangerously-allow-all-builds
```

Patch Changes

Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #9424.
Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.

`v10.8.1`

Compare Source

Patch Changes

Removed bright white highlighting, which didn't look good on some light themes #9389.
If there is no pnpm related configuration in package.json, onlyBuiltDependencies will be written to pnpm-workspace.yaml file #9404.

`v10.8.0`

Compare Source

Minor Changes

Experimental. A new hook is supported for updating configuration settings. The hook can be provided via .pnpmfile.cjs. For example:

module.exports = {
  hooks: {
    updateConfig: (config) => ({
      ...config,
      nodeLinker: "hoisted",
    }),
  },
};

Now you can use the pnpm add command with the --config flag to install new configurational dependencies #9377.

Patch Changes

Do not hang indefinitely, when there is a glob that starts with !/ in pnpm-workspace.yaml. This fixes a regression introduced by #9169.
pnpm audit --fix should update the overrides in pnpm-workspace.yaml.
pnpm link should update overrides in pnpm-workspace.yaml, not in package.json #9365.

`v10.7.1`: pnpm 10.7.1

Compare Source

Patch Changes

pnpm config set should convert the settings to their correct type before adding them to pnpm-workspace.yaml #9355.
pnpm config get should read auth related settings via npm CLI #9345.
Replace leading ~/ in a path in .npmrc with the home directory #9217.

Platinum Sponsors

Gold Sponsors

`v10.7.0`

Compare Source

Minor Changes

pnpm config get and list also show settings set in pnpm-workspace.yaml files #9316.
It should be possible to use env variables in pnpm-workspace.yaml setting names and value.
Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

For example:
```
patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  [email protected]: patches/foo-3.patch
```
The above configuration would apply patches/foo-3.patch to [email protected], patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.
[!WARNING]
The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:
```
# pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  '[email protected]': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch
```
In most cases, however, it's sufficient to just define an exact version to override the range.
pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #9316.
Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.
Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

Remove dependency paths from audit output to prevent out-of-memory errors #9280.

`v10.6.5`

Compare Source

Patch Changes

Remove warnings after having explicitly approved no builds #9296.
When installing different dependency packages, should retain the ignoredBuilds field in the .modules.yaml file #9240.
Fix usages of the catalog: protocol in injected local workspace packages. This previously errored with ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER. #8715
Setting workspace-concurrency to less than or equal to 0 should work #9297.

`v10.6.4`

Compare Source

Patch Changes

Fix pnpm dlx with --allow-build flag #9263.
Invalid Node.js version in use-node-version should not cause pnpm itself to break #9276.
The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

`v10.6.3`

Compare Source

Patch Changes

pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #9233. This fixes regression introduced via #9211.
Add the missing node-options config to recursive run #9180.
Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

See details in #9259.

`v10.6.2`

Compare Source

Patch Changes

pnpm self-update should always update the version in the packageManager field of package.json.
Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #8971.
pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
Don't show info output when --loglevel=error is used.
peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

`v10.6.1`

Compare Source

Patch Changes

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 ignore pnpm.patchedDependencies from package.json #9226.
When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.
When a package version cannot be found in the package metadata, print the registry from which the package was fetched.

`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:
```
verifyDepsBeforeRun: install
optimisticRepeatInstall: true
publicHoistPattern:
  - "*types*"
  - "!@&#8203;types/react"
```
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 a file: 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 with tinyglobby to reduce the size of the pnpm CLI dependencies #9169.
pnpm deploy should not remove fields from the deployed package's package.json file #9215.
pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
Fix pnpm deploy creating a package.json without the imports and license field #9193.
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

`v10.5.2`

Compare Source

Patch Changes

The pnpm config set command should change the global .npmrc file by default.
This was a regression introduced by #9151 and shipped in pnpm v10.5.0.

Configuration

📅 Schedule: Branch creation - "after 1am and before 5am" in timezone EST, 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.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

bolt-new-by-stackblitz · 2025-06-07T08:40:50Z

Run & review this pull request in StackBlitz Codeflow.

changeset-bot · 2025-06-07T08:40:51Z

⚠️ No Changeset found

Latest commit: 2596a0f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

github-actions · 2025-06-07T08:41:55Z

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
svelte-ux	✅ Ready (View Log)	Visit Preview	`2596a0f`

pkg-pr-new · 2025-06-07T08:42:10Z

Open in StackBlitz

npm i https://pkg.pr.new/svelte-ux@601

commit: 2596a0f

renovate bot added the dependencies label Jun 7, 2025

github-actions bot deployed to Preview June 7, 2025 08:41 View deployment

renovate bot force-pushed the renovate/pnpm-10.x branch from c76e281 to bf72c96 Compare June 8, 2025 17:27

renovate bot changed the title ~~chore(deps): update pnpm to v10.11.1~~ chore(deps): update pnpm to v10.12.1 Jun 8, 2025

github-actions bot deployed to Preview June 8, 2025 17:28 View deployment

chore(deps): update pnpm to v10.12.2

2596a0f

renovate bot force-pushed the renovate/pnpm-10.x branch from bf72c96 to 2596a0f Compare June 23, 2025 02:51

renovate bot changed the title ~~chore(deps): update pnpm to v10.12.1~~ chore(deps): update pnpm to v10.12.2 Jun 23, 2025

github-actions bot deployed to Preview June 23, 2025 02:52 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

chore(deps): update pnpm to v10.12.2 #601

chore(deps): update pnpm to v10.12.2 #601

Uh oh!

renovate bot commented Jun 7, 2025 •

edited

Loading

Uh oh!

bolt-new-by-stackblitz bot commented Jun 7, 2025

Uh oh!

changeset-bot bot commented Jun 7, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Jun 7, 2025 •

edited

Loading

Uh oh!

pkg-pr-new bot commented Jun 7, 2025 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

chore(deps): update pnpm to v10.12.2 #601

Are you sure you want to change the base?

chore(deps): update pnpm to v10.12.2 #601

Uh oh!

Conversation

renovate bot commented Jun 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

v10.7.1: pnpm 10.7.1

Patch Changes

Platinum Sponsors

Gold Sponsors

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

bolt-new-by-stackblitz bot commented Jun 7, 2025

Uh oh!

changeset-bot bot commented Jun 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

github-actions bot commented Jun 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Uh oh!

pkg-pr-new bot commented Jun 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

renovate bot commented Jun 7, 2025 •

edited

Loading

`v10.7.1`: pnpm 10.7.1

changeset-bot bot commented Jun 7, 2025 •

edited

Loading

github-actions bot commented Jun 7, 2025 •

edited

Loading

pkg-pr-new bot commented Jun 7, 2025 •

edited

Loading