Packages/pnpm

Releases of pnpm

1030 stable releases, newest first. Release notes are kept for the last 90 days; older ones link to where they were published.

  1. 11.15.1

    19 July 2026
  2. 11.15.0

    18 July 2026
  3. 11.14.0

    17 July 2026
  4. 11.13.1

    16 July 2026
  5. 11.13.0

    13 July 2026
  6. 11.12.0

    11 July 2026
  7. 11.11.0

    9 July 2026
  8. 11.10.0

    4 July 2026
  9. 11.9.0

    23 June 2026
  10. 11.8.0

    18 June 2026
  11. 11.7.0

    15 June 2026
  12. 11.6.0

    11 June 2026
  13. 11.5.3

    10 June 2026
  14. 11.5.2

    5 June 2026
  15. 11.5.1

    2 June 2026
  16. 11.5.0

    29 May 2026
  17. 11.4.0

    27 May 2026
  18. 11.3.0

    24 May 2026
  19. 11.2.2

    21 May 2026
  20. 11.2.1

    20 May 2026
  21. 11.2.0

    20 May 2026
  22. 11.1.3

    18 May 2026
  23. 11.1.2

    14 May 2026
  24. 11.1.1

    12 May 2026
  25. 11.1.0

    11 May 2026
  26. 11.0.9

    9 May 2026
  27. 11.0.8

    7 May 2026
  28. 11.0.7

    6 May 2026
  29. 11.0.6

    5 May 2026
  30. 11.0.5

    4 May 2026
  31. 11.0.4

    2 May 2026
  32. 11.0.3

    30 April 2026
  33. 11.0.2

    30 April 2026
  34. 11.0.1

    29 April 2026
  35. 11.0.0

    28 April 2026
  36. 10.34.7

    12 October 2026

    Patch Changes

    • 97f550c: Switching to the pnpm version in packageManager now works through registry mirrors that strip npm's signatures or re-sign packages with their own key. pnpm then reads the signature from https://registry.npmjs.org/ and verifies it against the integrity of the downloaded pnpm #16778.

    • b11d7bb: The update notification now suggests the standalone install script instead of pnpm self-update when PNPM_HOME is not set, such as when another package manager installed pnpm. pnpm self-update installs into PNPM_HOME, so in that case it cannot replace the pnpm in use.

  37. 10.34.6

    28 September 2026

    Generated from commits

    Patch Changes

    • e7888e5: pnpm self-update now resolves and verifies pnpm through registry, authentication, proxy, and TLS settings from trusted non-project configuration. Project configuration and the default project pnpmfile can no longer redirect the pnpm download or disable engine identity verification.

    • 46bc7c9: pnpm no longer tells you to update itself with Corepack or with pnpm add -g:

      • The update notification now suggests pnpm self-update, or the standalone install script when pnpm is running under Corepack. It used to suggest corepack use pnpm@<version>, or pnpm add -g pnpm / pnpm add -g @pnpm/exe when pnpm was not installed by the standalone script — but pnpm add -g refuses to install pnpm and points at pnpm self-update anyway, and @pnpm/exe is not published for pnpm v12 or newer, where the unscoped pnpm package is itself the native executable.

      • pnpm self-update under Corepack now points at the standalone install script too, instead of telling you to update pnpm with Corepack.

    • security

      46bc7c9: Updated adm-zip to v0.6.0, which fixes a memory-exhaustion vulnerability where a crafted ZIP file could make it allocate 4 GB of memory. adm-zip is used to extract the Node.js, Bun, and Deno archives that pnpm downloads on Windows.

  38. 10.34.5

    10 July 2026
  39. 10.34.4

    18 June 2026
  40. 10.34.3

    11 June 2026
  41. 10.34.2

    10 June 2026
  42. 10.34.1

    27 May 2026
  43. 10.34.0

    27 May 2026
  44. 10.33.4

    6 May 2026
  45. 10.33.3

    4 May 2026
  46. 10.33.2

    23 April 2026
  47. 10.33.1

    22 April 2026
  48. 10.33.0

    24 March 2026
  49. 10.32.1

    11 March 2026
  50. 10.32.0

    9 March 2026