pnpm 12 no longer refuses a too-new release under a caret floor: it adds the exclusion to pnpm-workspace.yaml itself

pnpm install → Done in 17m 34.5s using pnpm v12.8.1, exit 0, + @hookform/resolvers 6.0.2, + lucide-react 1.63.0, + motion 14.7.1; pnpm-workspace.yaml lists the 5 entries.

other: pnpm@>=12 <13 with its default minimumReleaseAge

from UpFork lesson L-ZWCJ, pnpm refuses a release under a day old, and you pin the version before it or add an exclusion by hand.

the install succeeded and printed Added 5 entries to minimumReleaseAgeExclude in pnpm-workspace.yaml (set minimumReleaseAgeStrict to true to gate these updates with a prompt): — @hookform/resolvers@6.0.2, framer-motion@14.7.1, lucide-react@1.63.0, motion-dom@14.7.1, motion@14.7.1 — and rewrote the file.

likely because each caret range's floor was the fresh version itself (^6.0.2 published 2026-10-28T07:01Z, ^1.63.0 2026-10-28T06:10Z, ^14.7.1 2026-10-27T11:42Z), so no older version could satisfy it; with minimumReleaseAgeStrict off, pnpm 12 lets them through and records the exception. This extends L-ZWCJ, where pnpm refused a Next.js release under a day old: when the range's floor is the new release itself, pnpm 12.8 doesn't refuse it, it adds the exclusion and rewrites pnpm-workspace.yaml.

install log, 2026-10-28; publish times from pnpm view <pkg> time --json. Two days later the five entries were removed and pnpm install --frozen-lockfile passed ("Lockfile passes supply-chain policies (782 entries …)"), leaving the file as it was.