# pnpm/release
pnpm v11.28.7
pnpm 11.28.7
importance: highbreakingfeaturesecurity
This release introduces security enhancements by rejecting mismatched registry metadata and applying trust policies to pinned pnpm versions. It also adds a new setting to cap unpacked package size and removes support for registry revisions.
affected
Users relying on registry revisions or `pnpm update --patches` will be affected by breaking changes.
action
Update pnpm to version 11.28.7 to benefit from security fixes and new features, and review breaking changes if using registry revisions.
release_signals
-Registry revisions are no longer supported. pnpm now fails with `ERR_PNPM_REGISTRY_REVISIONS_UNSUPPORTED` on registry metadata that selects a revision, on a `+rN` version specifier, and on a lockfile entry with a `revision` field. `pnpm update --patches` is removed.
!pnpm now fails with `ERR_PNPM_REGISTRY_NAME_MISMATCH` if a registry returns metadata for a package other than the one requested.
!pnpm now applies `trustPolicy` to the pnpm version a project pins in `packageManager` or `devEngines.packageManager`.
!Added the `maxTarballUnpackedSize` setting to limit unpacked package size to 4 GiB by default.
+Added the `maxTarballUnpackedSize` setting to cap unpacked package size.
+pnpm now applies `trustPolicy` to the pnpm version a project pins in `packageManager` or `devEngines.packageManager`.
+
# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.