●Change8

Migrating to pnpm v11.0.0-rc.3

Version v11.0.0-rc.3 introduces 1 breaking change. This guide details how to update your code.

Released: 4/20/2026

1
Breaking Changes
3
Migration Steps
10
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

`pnpm pack-app``pnpm audit --fix``pnpm version``@pnpm/exe``@pnpm/linux-x64``@pnpm/exe.linux-x64``pnpm sbom``pnpm licenses``pnpm add -g``@pnpm/deps.compliance.license-resolver`

Breaking Changes

●Issue #1

Overrides emitted by `pnpm audit --fix` now use a caret range (^X.Y.Z) instead of an open-ended >=X.Y.Z, which prevents silently promoting a dependency across a major version boundary when fixing vulnerabilities.

Migration Steps

  1. 1
    If you rely on the exact behavior of `pnpm audit --fix` ignoring `auditLevel`, be aware that it now respects it. If you want to fix everything, use `pnpm audit --fix --severity=info` (or the appropriate level).
  2. 2
    If you download pnpm releases directly, note that platform-specific optional dependency package names and release asset filenames have been renamed to use the `pnpm/exe.<platform>-<arch>[-<libc>]` scheme (e.g., `@pnpm/linux-x64` is now `@pnpm/exe.linux-x64`).
  3. 3
    If you were relying on `pnpm licenses` preferring the deprecated `licenses` array over the `license` field in package.json, note that both `pnpm sbom` and `pnpm licenses` now prefer the modern `license` field.

Release Summary

This release introduces the `pnpm pack-app` command for creating standalone executables and significantly enhances `pnpm version` to better align with npm's CLI behavior. It also refines security auditing, dependency resolution for git sources, and updates internal platform naming conventions.

Need More Details?

View the full release notes and all changes for pnpm v11.0.0-rc.3.

View Full Changelog