pnpm / update detail

pnpm 11.6

Official pnpm changelog summary with source attribution, release tags, and community reactions.

Track this pnpm release note alongside related changelog updates, risky changes, and weekly digest signals from the developer community.

pnpm·2 months ago · Jun 11, 2026, 11:08 PMFixSecurity-relevantAI-assisted summary

pnpm 11.6

Summary

Stop expanding ${VAR} placeholders from repository‑controlled .npmrc files to prevent secret leakage (security fix).
Treat the lockfile stored in node_modules/.pnpm/lock.yaml as the wanted lockfile, enabling “already up‑to‑date” detection when pnpm‑lock.yaml is missing (minor improvement).
Add support for URL‑scoped registry settings via environment variables, raise default network concurrency, improve warnings, and skip optional dependencies with missing platform metadata (feature and bugfix).

securityfeatureminorbugfixsource healthy

Official source Last checked 14 hours ago

Loading follow options…

official source

Verify the original release note

Every summary should remain traceable to the original changelog or release source.

AI-assisted summarysource healthyLast checked 14 hours ago

Official changelog

related channels

Follow this in context

Turn this pnpm release note into a weekly digest for the tools you actually use.

Create digest

related updates

More pnpm changelog updates

Product page

pnpm·1 week agoFix

Added a pnpm cache‑path command, new setting minimumReleaseAgeExcludePrune, and renamed cleanupUnusedCatalogs to catalogPrune; workspace.yaml can no longer configure various directories and now warns about ignored settings.

Official source

pnpm·2 weeks agoFix

pnpm 11.21

Summary

Added interactive group selection for `pnpm update --global` and introduced sudo warnings for global commands to prevent accidental root installations.

Official source

pnpm·3 weeks agoFixMay break your integration

pnpm 11.20

Summary

Introduce registry‑qualified keys for packages from named registries to prevent substitution attacks, requiring a lockfile diff and coordinated upgrade

securitybreaking

Official source

pnpm / update detail

pnpm 11.6

Official pnpm changelog summary with source attribution, release tags, and community reactions.

Track this pnpm release note alongside related changelog updates, risky changes, and weekly digest signals from the developer community.

pnpm·2 months ago · Jun 11, 2026, 11:08 PMFixSecurity-relevantAI-assisted summary

pnpm 11.6

Summary

Stop expanding ${VAR} placeholders from repository‑controlled .npmrc files to prevent secret leakage (security fix).
Treat the lockfile stored in node_modules/.pnpm/lock.yaml as the wanted lockfile, enabling “already up‑to‑date” detection when pnpm‑lock.yaml is missing (minor improvement).
Add support for URL‑scoped registry settings via environment variables, raise default network concurrency, improve warnings, and skip optional dependencies with missing platform metadata (feature and bugfix).

securityfeatureminorbugfixsource healthy

Official source Last checked 14 hours ago

Loading follow options…

official source

Verify the original release note

Every summary should remain traceable to the original changelog or release source.

AI-assisted summarysource healthyLast checked 14 hours ago

Official changelog

related channels

Follow this in context

Turn this pnpm release note into a weekly digest for the tools you actually use.

Create digest

related updates

More pnpm changelog updates

Product page

pnpm·1 week agoFix

pnpm 11.22

Summary

Official source

pnpm·2 weeks agoFix

pnpm 11.21

Summary

Added interactive group selection for `pnpm update --global` and introduced sudo warnings for global commands to prevent accidental root installations.

Official source

pnpm·3 weeks agoFixMay break your integration

pnpm 11.20

Summary

Introduce registry‑qualified keys for packages from named registries to prevent substitution attacks, requiring a lockfile diff and coordinated upgrade

securitybreaking

Official source