? Verifying lockfile against supply-chain policies (412 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +241 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 241, reused 0, downloaded 53, added 0 Progress: resolved 241, reused 0, downloaded 184, added 12 Progress: resolved 241, reused 0, downloaded 241, added 208 ✗ Lockfile failed supply-chain policy check (412 entries in 3.1s) Progress: resolved 241, reused 0, downloaded 241, added 241, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 17 lockfile entries failed verification: @tailwindcss/node@4.3.3 was published at 2026-07-16T12:03:43.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-android-arm64@4.3.3 was published at 2026-07-16T12:02:13.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-darwin-arm64@4.3.3 was published at 2026-07-16T12:02:19.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-darwin-x64@4.3.3 was published at 2026-07-16T12:02:26.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-freebsd-x64@4.3.3 was published at 2026-07-16T12:02:35.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-linux-arm-gnueabihf@4.3.3 was published at 2026-07-16T12:02:41.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-linux-arm64-gnu@4.3.3 was published at 2026-07-16T12:02:47.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-linux-arm64-musl@4.3.3 was published at 2026-07-16T12:02:54.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-linux-x64-gnu@4.3.3 was published at 2026-07-16T12:03:05.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-linux-x64-musl@4.3.3 was published at 2026-07-16T12:03:12.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-wasm32-wasi@4.3.3 was published at 2026-07-16T12:04:13.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-win32-arm64-msvc@4.3.3 was published at 2026-07-16T12:03:17.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide-win32-x64-msvc@4.3.3 was published at 2026-07-16T12:03:22.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/oxide@4.3.3 was published at 2026-07-16T12:03:26.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) @tailwindcss/vite@4.3.3 was published at 2026-07-16T12:04:04.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) tailwindcss@4.3.3 was published at 2026-07-16T12:03:32.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) vite@8.1.5 was published at 2026-07-16T06:51:09.000Z, within the minimumReleaseAge cutoff (2026-07-15T14:09:27.029Z) 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.