Migrating to pnpm v12.0.0-alpha.18
Version v12.0.0-alpha.18 introduces 1 breaking change. This guide details how to update your code.
Released: 7/22/2026
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
pnpm versionpnpm outdatedpnpm listpnpm llpnpm rebuildpnpm whypnpm peerspnpm updatepnpm installpnpm addpnpm removepnpm unlinkpnpm-workspace.yamlpnpm-lock.yamlcatalog: protocolpnpm/pnpm#13193Breaking Changes
●Issue #1
The behavior of the first release of a package has changed. It now publishes the version written in its manifest verbatim, instead of automatically bumping it. This means a package seeded at `1100.0.0` with a `minor` changeset will be published as `1100.0.0` and not `1100.1.0`. This affects how initial versions are handled and may require adjustments in CI/CD pipelines that expect automatic version bumping on first release.
Migration Steps
- 1Update `pnpm-workspace.yaml` to use the new `update` and `audit` sections instead of `updateConfig`, `auditConfig`, and `auditLevel` to avoid deprecation warnings in the future. For example, change `updateConfig.ignoreDependencies` to `update.ignoreDeps` and `auditLevel` to `audit.level`.
Release Summary
This release introduces significant improvements to recursive workspace operations, enhanced versioning capabilities with `pnpm version`, and a new changeset generation feature for `pnpm update`. It also addresses several bugs related to dependency resolution and lockfile management.
Need More Details?
View the full release notes and all changes for pnpm v12.0.0-alpha.18.
View Full Changelog