pnpm v11.28.10
pnpm 11.28.10
This patch release fixes `pnpm store prune` deleting unrelated stores or global package data when `cacheDir` points to their parent, and resolves multiple install, lockfile, and command-execution issues. It also improves handling of globally installed commands, workspace dependency changes, Node.js downloads, and platform-specific command shims.
Users of global installs, workspace and local dependencies, lockfiles, store pruning, and pnpm command execution may see these fixes; affected dependency cycles may incur a one-time rebuild-cache miss.
Upgrade to pnpm 11.28.10; reinstall affected globally installed packages with `pnpm add --global`.
- 01Reinstall globally installed packages with `pnpm add --global` to update existing commands that load dependencies hoisted for their package.
- 02After this update, packages in a dependency cycle and packages depending on them move to new global virtual store directories once; packages that run a build miss the side-effects cache once.
# community_signal
How useful is this release to your stack?
Sign in with GitHub to cast your vote.
You’ll return to this release, then choose your vote.