Command "vp install" (cwd: /home/runner/work/BlockNote/BlockNote) exited with code 1

Scope: all 126 workspace projects ? Verifying lockfile against supply-chain policies (2078 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1828 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1828, reused 518, downloaded 0, added 0 Progress: resolved 1828, reused 993, downloaded 0, added 0 Progress: resolved 1828, reused 1329, downloaded 0, added 0 Progress: resolved 1828, reused 1627, downloaded 0, added 0 Progress: resolved 1828, reused 1798, downloaded 28, added 7 Progress: resolved 1828, reused 1798, downloaded 28, added 375 Progress: resolved 1828, reused 1798, downloaded 28, added 680 Progress: resolved 1828, reused 1798, downloaded 28, added 998 ✗ Lockfile failed supply-chain policy check (2078 entries in 8.9s) Progress: resolved 1828, reused 1798, downloaded 28, added 1111 Progress: resolved 1828, reused 1798, downloaded 28, added 1760 Progress: resolved 1828, reused 1798, downloaded 28, added 1828, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification: @ai-sdk/provider-utils@4.0.54 was published at 2026-09-23T21:55:30.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:08.040Z) baseline-browser-mapping@2.11.26 was published at 2026-09-24T18:18:25.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:08.040Z) caniuse-lite@1.0.30001812 was published at 2026-09-24T06:46:03.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:08.040Z) prosemirror-dropcursor@1.8.4 was published at 2026-09-24T08:32:31.785Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:08.040Z) webpack-sources@3.5.3 was published at 2026-09-24T18:45:17.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:08.040Z) 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.

Command "vp install" (cwd: /home/runner/work/BlockNote/BlockNote) exited with code 1

Scope: all 126 workspace projects ? Verifying lockfile against supply-chain policies (2078 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1828 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1828, reused 604, downloaded 0, added 0 Progress: resolved 1828, reused 1023, downloaded 0, added 0 Progress: resolved 1828, reused 1380, downloaded 0, added 0 Progress: resolved 1828, reused 1769, downloaded 0, added 0 Progress: resolved 1828, reused 1798, downloaded 28, added 119 Progress: resolved 1828, reused 1798, downloaded 28, added 471 Progress: resolved 1828, reused 1798, downloaded 28, added 820 Progress: resolved 1828, reused 1798, downloaded 28, added 1023 ✗ Lockfile failed supply-chain policy check (2078 entries in 8.6s) Progress: resolved 1828, reused 1798, downloaded 28, added 1376 Progress: resolved 1828, reused 1798, downloaded 28, added 1828, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification: @ai-sdk/provider-utils@4.0.54 was published at 2026-09-23T21:55:30.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:09.126Z) baseline-browser-mapping@2.11.26 was published at 2026-09-24T18:18:25.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:09.126Z) caniuse-lite@1.0.30001812 was published at 2026-09-24T06:46:03.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:09.126Z) prosemirror-dropcursor@1.8.4 was published at 2026-09-24T08:32:31.785Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:09.126Z) webpack-sources@3.5.3 was published at 2026-09-24T18:45:17.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:06:09.126Z) 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.

Command "vp install" (cwd: /__w/BlockNote/BlockNote) exited with code 1

Scope: all 126 workspace projects ? Verifying lockfile against supply-chain policies (2078 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1828 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1828, reused 564, downloaded 0, added 0 Progress: resolved 1828, reused 984, downloaded 0, added 0 Progress: resolved 1828, reused 1271, downloaded 0, added 0 Progress: resolved 1828, reused 1597, downloaded 0, added 0 Progress: resolved 1828, reused 1798, downloaded 20, added 4 Progress: resolved 1828, reused 1798, downloaded 28, added 276 Progress: resolved 1828, reused 1798, downloaded 28, added 568 Progress: resolved 1828, reused 1798, downloaded 28, added 878 ✗ Lockfile failed supply-chain policy check (2078 entries in 8.9s) Progress: resolved 1828, reused 1798, downloaded 28, added 1110 Progress: resolved 1828, reused 1798, downloaded 28, added 1726 Progress: resolved 1828, reused 1798, downloaded 28, added 1828, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 5 lockfile entries failed verification: @ai-sdk/provider-utils@4.0.54 was published at 2026-09-23T21:55:30.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:07:27.357Z) baseline-browser-mapping@2.11.26 was published at 2026-09-24T18:18:25.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:07:27.357Z) caniuse-lite@1.0.30001812 was published at 2026-09-24T06:46:03.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:07:27.357Z) prosemirror-dropcursor@1.8.4 was published at 2026-09-24T08:32:31.785Z, within the minimumReleaseAge cutoff (2026-09-23T20:07:27.357Z) webpack-sources@3.5.3 was published at 2026-09-24T18:45:17.000Z, within the minimumReleaseAge cutoff (2026-09-23T20:07:27.357Z) 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.

No files were found with the provided path: tests/playwright-report/. No artifacts will be uploaded.

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"