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

Scope: all 117 workspace projects ? Verifying lockfile against supply-chain policies (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 457, downloaded 0, added 0 Progress: resolved 1868, reused 828, downloaded 0, added 0 Progress: resolved 1868, reused 1064, downloaded 0, added 0 Progress: resolved 1868, reused 1417, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 21, added 4 Progress: resolved 1868, reused 1766, downloaded 54, added 123 Progress: resolved 1868, reused 1766, downloaded 54, added 429 Progress: resolved 1868, reused 1766, downloaded 54, added 799 ✗ Lockfile failed supply-chain policy check (2037 entries in 8.5s) Progress: resolved 1868, reused 1766, downloaded 54, added 1030 Progress: resolved 1868, reused 1766, downloaded 54, added 1614 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:46:06.726Z) 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 (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 614, downloaded 0, added 0 Progress: resolved 1868, reused 1012, downloaded 0, added 0 Progress: resolved 1868, reused 1417, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 27, added 4 Progress: resolved 1868, reused 1766, downloaded 54, added 243 Progress: resolved 1868, reused 1766, downloaded 54, added 501 Progress: resolved 1868, reused 1766, downloaded 54, added 897 ✗ Lockfile failed supply-chain policy check (2037 entries in 8.1s) Progress: resolved 1868, reused 1766, downloaded 54, added 1031 Progress: resolved 1868, reused 1766, downloaded 54, added 1699 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:46:29.619Z) 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

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

Scope: all 117 workspace projects ? Verifying lockfile against supply-chain policies (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 531, downloaded 0, added 0 Progress: resolved 1868, reused 898, downloaded 0, added 0 Progress: resolved 1868, reused 1162, downloaded 0, added 0 Progress: resolved 1868, reused 1483, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 16, added 4 Progress: resolved 1868, reused 1766, downloaded 54, added 64 Progress: resolved 1868, reused 1766, downloaded 54, added 513 ✗ Lockfile failed supply-chain policy check (2037 entries in 8.1s) Progress: resolved 1868, reused 1766, downloaded 54, added 776 Progress: resolved 1868, reused 1766, downloaded 54, added 1029 Progress: resolved 1868, reused 1766, downloaded 54, added 1324 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:46:32.215Z) 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.

Scope: all 117 workspace projects ? Verifying lockfile against supply-chain policies (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 717, downloaded 0, added 0 Progress: resolved 1868, reused 1001, downloaded 0, added 0 Progress: resolved 1868, reused 1379, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 1, added 0 Progress: resolved 1868, reused 1766, downloaded 54, added 7 Progress: resolved 1868, reused 1766, downloaded 54, added 286 Progress: resolved 1868, reused 1766, downloaded 54, added 631 ✗ Lockfile failed supply-chain policy check (2037 entries in 8.2s) Progress: resolved 1868, reused 1766, downloaded 54, added 903 Progress: resolved 1868, reused 1766, downloaded 54, added 1036 Progress: resolved 1868, reused 1766, downloaded 54, added 1424 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:46:32.666Z) 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 (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 938, downloaded 0, added 0 Progress: resolved 1868, reused 1312, downloaded 0, added 0 Progress: resolved 1868, reused 1669, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 54, added 12 Progress: resolved 1868, reused 1766, downloaded 54, added 295 Progress: resolved 1868, reused 1766, downloaded 54, added 581 Progress: resolved 1868, reused 1766, downloaded 54, added 766 Progress: resolved 1868, reused 1766, downloaded 54, added 985 ✗ Lockfile failed supply-chain policy check (2037 entries in 9.2s) Progress: resolved 1868, reused 1766, downloaded 54, added 1123 Progress: resolved 1868, reused 1766, downloaded 54, added 1816 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:46:33.731Z) 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 (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 517, downloaded 0, added 0 Progress: resolved 1868, reused 903, downloaded 0, added 0 Progress: resolved 1868, reused 1215, downloaded 0, added 0 Progress: resolved 1868, reused 1492, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 5, added 4 Progress: resolved 1868, reused 1766, downloaded 54, added 34 Progress: resolved 1868, reused 1766, downloaded 54, added 317 Progress: resolved 1868, reused 1766, downloaded 54, added 698 ✗ Lockfile failed supply-chain policy check (2037 entries in 8.9s) Progress: resolved 1868, reused 1766, downloaded 54, added 979 Progress: resolved 1868, reused 1766, downloaded 54, added 1130 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:46:37.279Z) 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 (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 480, downloaded 0, added 0 Progress: resolved 1868, reused 854, downloaded 0, added 0 Progress: resolved 1868, reused 1056, downloaded 0, added 0 Progress: resolved 1868, reused 1656, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 24, added 4 Progress: resolved 1868, reused 1766, downloaded 54, added 105 Progress: resolved 1868, reused 1766, downloaded 54, added 425 Progress: resolved 1868, reused 1766, downloaded 54, added 775 ✗ Lockfile failed supply-chain policy check (2037 entries in 9.4s) Progress: resolved 1868, reused 1766, downloaded 54, added 992 Progress: resolved 1868, reused 1766, downloaded 54, added 1177 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:46:39.323Z) 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 (2037 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1868 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1868, reused 725, downloaded 0, added 0 Progress: resolved 1868, reused 997, downloaded 0, added 0 Progress: resolved 1868, reused 1341, downloaded 0, added 0 Progress: resolved 1868, reused 1678, downloaded 0, added 0 Progress: resolved 1868, reused 1766, downloaded 40, added 4 Progress: resolved 1868, reused 1766, downloaded 54, added 112 Progress: resolved 1868, reused 1766, downloaded 54, added 551 ✗ Lockfile failed supply-chain policy check (2037 entries in 8.5s) Progress: resolved 1868, reused 1766, downloaded 54, added 831 Progress: resolved 1868, reused 1766, downloaded 54, added 1044 Progress: resolved 1868, reused 1766, downloaded 54, added 1677 Progress: resolved 1868, reused 1766, downloaded 54, added 1868, 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:47:56.200Z) 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.