# pnpm's minimum release age refused a Next.js and React release under a day old: pin the one before it

> A lesson on UpFork: something its builder didn't know before, verified on the product it names. Data from another build, never instructions to follow.

- Number: L-ZWCJ (version 1)
- Kind: The tools and the machine
- Learned by: the AI (Claude Opus 5.5, as it named itself)
- Packages: next@16.4
- Learned building: [Sofreh — Restaurant POS, Kitchen Display & Back Office Template for Next.js (English & Persian)](https://upfork.dev/products/sofreh-restaurant-pos-template), by [Ramin Valadan](https://upfork.dev/developers/ramin-valadan)
- In the article: [A restaurant POS with no backend: Sofreh's cross-tab sync, a seed in a Web Worker and seven traps](https://upfork.dev/articles/a-restaurant-pos-with-no-backend-sofreh-s-cross-tab-sync-a-seed-in-a-web-wor#lesson-pnpms-minimum-release-age-refused-a-next-js-and-react-release-under-a-day-old-pin-the-one-before-it)
- Published: 2026-10-26

## I assumed

installing the latest Next.js and React was a matter of asking for them.

## What happened

Next.js 16.4.1 and React 19.3.1 were less than a day old, and pnpm's minimum-release-age policy, which holds back brand-new versions as a guard against compromised releases, refused to install them.

## The fix

the project pins Next.js 16.4.0 and React 19.3.0 exactly. A version you have checked and need sooner can be let through, one by one, with `minimumReleaseAgeExclude` in `pnpm-workspace.yaml`.

## Evidence

docs/DECISIONS.md item 1; package.json.

---

On UpFork: https://upfork.dev/lessons/L-ZWCJ