…(truncated, showing last 4000 chars)… fying lockfile against supply-chain policies (411 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +207 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 207, reused 0, downloaded 11, added 0 Packages are hard linked from the content-addressable store to the virtual store. Content-addressable store is at: /home/runner/.local/share/pnpm/store/v11 Virtual store is at: node_modules/.pnpm Progress: resolved 207, reused 0, downloaded 107, added 4 Progress: resolved 207, reused 0, downloaded 207, added 207, done ✗ Lockfile failed supply-chain policy check (411 entries in 3.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 19 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.77.0 was published at 2026-08-03T12:05:07.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-android-arm64@1.77.0 was published at 2026-08-03T12:04:06.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-darwin-arm64@1.77.0 was published at 2026-08-03T12:03:59.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-darwin-x64@1.77.0 was published at 2026-08-03T12:06:20.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-freebsd-x64@1.77.0 was published at 2026-08-03T12:06:34.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-arm-gnueabihf@1.77.0 was published at 2026-08-03T12:05:17.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-arm-musleabihf@1.77.0 was published at 2026-08-03T12:05:23.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-arm64-gnu@1.77.0 was published at 2026-08-03T12:04:42.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-arm64-musl@1.77.0 was published at 2026-08-03T12:04:51.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-ppc64-gnu@1.77.0 was published at 2026-08-03T12:05:49.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-riscv64-gnu@1.77.0 was published at 2026-08-03T12:05:57.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-riscv64-musl@1.77.0 was published at 2026-08-03T12:06:05.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-s390x-gnu@1.77.0 was published at 2026-08-03T12:06:12.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-x64-gnu@1.77.0 was published at 2026-08-03T12:06:41.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-linux-x64-musl@1.77.0 was published at 2026-08-03T12:06:49.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-openharmony-arm64@1.77.0 was published at 2026-08-03T12:04:58.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-win32-arm64-msvc@1.77.0 was published at 2026-08-03T12:04:32.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-win32-ia32-msvc@1.77.0 was published at 2026-08-03T12:05:36.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) @oxlint/binding-win32-x64-msvc@1.77.0 was published at 2026-08-03T12:06:27.000Z, within the minimumReleaseAge cutoff (2026-08-02T22:34:16.698Z) 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.