On October 16, 2026 the npm `latest` tag for pnpm points to 12.11.2, so an unpinned install now gives you version 12 even though the official release notes still describe `latest-12` as the opt-in
A global pnpm 10.6.2 cannot switch to a repository pinned to `pnpm@12.11.2`: it fails with `spawnSync ... ENOEXEC`, and the cure is to run pnpm 12 itself.
`pnpm install --frozen-lockfile false` now errors with `unexpected argument '--frozen-lockfile'`, and an unknown key in `pnpm-workspace.yaml` stops the install with