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

Scope: all 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 527, downloaded 0, added 0 Progress: resolved 1870, reused 908, downloaded 0, added 0 Progress: resolved 1870, reused 1202, downloaded 0, added 0 Progress: resolved 1870, reused 1704, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 51, added 4 Progress: resolved 1870, reused 1765, downloaded 57, added 205 Progress: resolved 1870, reused 1765, downloaded 57, added 672 ✗ Lockfile failed supply-chain policy check (2039 entries in 8.2s) Progress: resolved 1870, reused 1765, downloaded 57, added 1007 Progress: resolved 1870, reused 1765, downloaded 57, added 1126 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:38:56.238Z) 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 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 696, downloaded 0, added 0 Progress: resolved 1870, reused 1001, downloaded 0, added 0 Progress: resolved 1870, reused 1387, downloaded 0, added 0 Progress: resolved 1870, reused 1752, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 57, added 28 Progress: resolved 1870, reused 1765, downloaded 57, added 408 Progress: resolved 1870, reused 1765, downloaded 57, added 704 ✗ Lockfile failed supply-chain policy check (2039 entries in 7.9s) Progress: resolved 1870, reused 1765, downloaded 57, added 1013 Progress: resolved 1870, reused 1765, downloaded 57, added 1119 Progress: resolved 1870, reused 1765, downloaded 57, added 1781 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:39:26.846Z) 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 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 522, downloaded 0, added 0 Progress: resolved 1870, reused 886, downloaded 0, added 0 Progress: resolved 1870, reused 1086, downloaded 0, added 0 Progress: resolved 1870, reused 1358, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 34, added 4 Progress: resolved 1870, reused 1765, downloaded 57, added 157 Progress: resolved 1870, reused 1765, downloaded 57, added 420 Progress: resolved 1870, reused 1765, downloaded 57, added 724 Progress: resolved 1870, reused 1765, downloaded 57, added 974 ✗ Lockfile failed supply-chain policy check (2039 entries in 9.5s) Progress: resolved 1870, reused 1765, downloaded 57, added 1119 Progress: resolved 1870, reused 1765, downloaded 57, added 1836 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:39:28.023Z) 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 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 1055, downloaded 0, added 0 Progress: resolved 1870, reused 1676, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 32, added 4 Progress: resolved 1870, reused 1765, downloaded 57, added 242 Progress: resolved 1870, reused 1765, downloaded 57, added 554 Progress: resolved 1870, reused 1765, downloaded 57, added 878 Progress: resolved 1870, reused 1765, downloaded 57, added 983 Progress: resolved 1870, reused 1765, downloaded 57, added 1089 ✗ Lockfile failed supply-chain policy check (2039 entries in 8.9s) Progress: resolved 1870, reused 1765, downloaded 57, added 1278 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:39:31.920Z) 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 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 578, downloaded 0, added 0 Progress: resolved 1870, reused 937, downloaded 0, added 0 Progress: resolved 1870, reused 1230, downloaded 0, added 0 Progress: resolved 1870, reused 1622, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 27, added 4 Progress: resolved 1870, reused 1765, downloaded 57, added 270 Progress: resolved 1870, reused 1765, downloaded 57, added 627 ✗ Lockfile failed supply-chain policy check (2039 entries in 7.6s) Progress: resolved 1870, reused 1765, downloaded 57, added 1030 Progress: resolved 1870, reused 1765, downloaded 57, added 1138 Progress: resolved 1870, reused 1765, downloaded 57, added 1823 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:39:32.706Z) 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 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 587, downloaded 0, added 0 Progress: resolved 1870, reused 948, downloaded 0, added 0 Progress: resolved 1870, reused 1220, downloaded 0, added 0 Progress: resolved 1870, reused 1573, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 32, added 4 Progress: resolved 1870, reused 1765, downloaded 57, added 182 Progress: resolved 1870, reused 1765, downloaded 57, added 520 ✗ Lockfile failed supply-chain policy check (2039 entries in 8.4s) Progress: resolved 1870, reused 1765, downloaded 57, added 833 Progress: resolved 1870, reused 1765, downloaded 57, added 1033 Progress: resolved 1870, reused 1765, downloaded 57, added 1657 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:39:32.863Z) 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 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 776, downloaded 0, added 0 Progress: resolved 1870, reused 1037, downloaded 0, added 0 Progress: resolved 1870, reused 1359, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 5, added 0 Progress: resolved 1870, reused 1765, downloaded 51, added 4 Progress: resolved 1870, reused 1765, downloaded 57, added 231 Progress: resolved 1870, reused 1765, downloaded 57, added 580 Progress: resolved 1870, reused 1765, downloaded 57, added 819 Progress: resolved 1870, reused 1765, downloaded 57, added 1031 ✗ Lockfile failed supply-chain policy check (2039 entries in 9.6s) Progress: resolved 1870, reused 1765, downloaded 57, added 1273 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:39:33.189Z) 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 117 workspace projects ? Verifying lockfile against supply-chain policies (2039 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1870 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1870, reused 569, downloaded 0, added 0 Progress: resolved 1870, reused 931, downloaded 0, added 0 Progress: resolved 1870, reused 1189, downloaded 0, added 0 Progress: resolved 1870, reused 1539, downloaded 0, added 0 Progress: resolved 1870, reused 1765, downloaded 10, added 4 Progress: resolved 1870, reused 1765, downloaded 57, added 13 Progress: resolved 1870, reused 1765, downloaded 57, added 295 Progress: resolved 1870, reused 1765, downloaded 57, added 632 ✗ Lockfile failed supply-chain policy check (2039 entries in 9s) Progress: resolved 1870, reused 1765, downloaded 57, added 972 Progress: resolved 1870, reused 1765, downloaded 57, added 1125 Progress: resolved 1870, reused 1765, downloaded 57, added 1854 Progress: resolved 1870, reused 1765, downloaded 57, added 1870, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: baseline-browser-mapping@2.11.4 was published at 2026-07-26T15:10:40.000Z, within the minimumReleaseAge cutoff (2026-07-25T16:40:45.120Z) 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/.vitest-attachments/. No artifacts will be uploaded.

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

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

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

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

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

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

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

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

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

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

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