2026-07-29 — pnpm 11 install policy (minimumReleaseAge)

Summary

  • Updated pnpm-workspace.yaml to set minimumReleaseAge: 0.

  • This prevents ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION when lockfile entries include very recently published package versions.

  • Tooling / manual setup / deployment docs were updated to reference the policy and the “install from the workspace root” rule.

Troubleshooting

If you still hit ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION after this change:

  1. Confirm your install is running from the repo root (where pnpm-workspace.yaml and pnpm-lock.yaml live).

  2. Verify pnpm-workspace.yaml includes minimumReleaseAge: 0.

  3. If a CI build uses a cached lockfile or stale workspace config, rebuild the install from scratch.