? Verifying lockfile against supply-chain policies (369 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +203 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 203, reused 0, downloaded 110, added 14 Progress: resolved 203, reused 0, downloaded 197, added 55 Progress: resolved 203, reused 0, downloaded 203, added 203, done ✗ Lockfile failed supply-chain policy check (369 entries in 3.2s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: tailwindcss@4.3.2 was published at 2026-06-29T14:29:59.000Z, within the minimumReleaseAge cutoff (2026-06-28T23:40:32.871Z) The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.