●Change8

Migrating to pnpm v10.34.0

Version v10.34.0 introduces 1 breaking change. This guide details how to update your code.

Released: 5/27/2026

1
Breaking Changes
1
Migration Steps
6
Affected Symbols

⚠️ Check Your Code

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

`pnpm install``pnpm install --update-checksums``pnpm update``--frozen-lockfile``--fix-lockfile``--prefix`

Breaking Changes

●Issue #1

Tarball integrity mismatches against the lockfile now cause `pnpm install` (non-frozen) to fail hard with `ERR_PNPM_TARBALL_INTEGRITY` instead of silently overwriting the lockfile integrity.

✓Solution

To refresh locked integrity values from the registry without failing, use the new opt-in flag: `pnpm install --update-checksums`.

Migration Steps

  1. 1
    If you relied on `pnpm install` silently overwriting lockfile integrity on mismatch, switch to using `pnpm install --update-checksums` for controlled integrity updates.

Release Summary

This release hardens security by defaulting integrity mismatches to failures and introduces an opt-in flag to update checksums. Several security vulnerabilities related to git resolutions, patch files, and dependency aliases were also fixed.

Need More Details?

View the full release notes and all changes for pnpm v10.34.0.

View Full Changelog