pnpm / update detail

pnpm 10.34.2

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 10, 2026, 02:04 PMChangeMay break your integrationAI-assisted summary

pnpm 10.34.2

Summary

Stops environment variable expansion in project/workspace .npmrc and pnpm workspace.yaml, preventing secret leakage; only trusted user/global/CLI/env configs can expand vars.
Bootstrap traffic now uses trusted registries and verifies npm registry signatures for downloaded pnpm versions and Node.js SHASUM signatures, tightening supply‑chain security.
Adds hardening such as rejecting reserved bin names, requiring trusted package identity for lifecycle scripts, and improving lockfile validation.

securitybreakingminorsource healthy

Official source Last checked 15 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 15 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 10.34.2

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 10, 2026, 02:04 PMChangeMay break your integrationAI-assisted summary

pnpm 10.34.2

Summary

Stops environment variable expansion in project/workspace .npmrc and pnpm workspace.yaml, preventing secret leakage; only trusted user/global/CLI/env configs can expand vars.
Bootstrap traffic now uses trusted registries and verifies npm registry signatures for downloaded pnpm versions and Node.js SHASUM signatures, tightening supply‑chain security.
Adds hardening such as rejecting reserved bin names, requiring trusted package identity for lifecycle scripts, and improving lockfile validation.

securitybreakingminorsource healthy

Official source Last checked 15 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 15 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