mirror of
https://github.com/pnpm/pnpm.git
synced 2026-07-20 12:42:38 -04:00
73707d2ecb
Two published v11 releases were broken in ways nothing in the pipeline checked, and both only surfaced once users upgraded onto them. 11.12.0 was packed by a pnpm that ignores the .pnpmfile.cjs beforePacking hook, so the bundled dependency fields survived into the published manifest. Resolving node-gyp then pulled a peer-suffixed snapshot into the env lockfile, and every upgrade onto 11.12.0 died in buildLockfileFromEnvLockfile (pnpm/pnpm#12955, pnpm/pnpm#12959). 11.12.0 and 11.13.0 also shipped `@pnpm/exe` platform packages with no native binary; setup.js exits 0 when the binary is missing, so the placeholder bin survived and only a real invocation caught it. Assert on the packed tarball that the published pnpm manifest declares no dependency fields, rather than trusting either stripper, since npm publishes are immutable. Then, in the Tag workflow, upgrade from the release line's current version onto the new one for both the `pnpm` and `@pnpm/exe` wrappers and run the resulting binary. The release workflow has already published under next-<major> at that point, so this reads the real registry artifact, and it runs before the dist-tags move — the last gate before a version reaches everyone. Verified against the registry: the assert rejects pnpm@11.12.0 and accepts 11.11.0/11.13.1; the upgrade gate passes 11.13.0 -> 11.13.1 and catches both `pnpm@11.12.0` and `@pnpm/exe@11.12.0`/11.13.0. Related to pnpm/pnpm#12959.