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

Scope: all 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 6.1s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:49:03.468Z) 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 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 7.2s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:49:29.462Z) 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 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 6.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:49:30.045Z) 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 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 6.5s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:49:33.737Z) 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 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 6.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:49:34.891Z) 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 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 8.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:49:34.507Z) 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 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 7.9s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:49:36.904Z) 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 111 workspace projects ? Verifying lockfile against supply-chain policies (1949 entries)... ✗ Lockfile failed supply-chain policy check (1949 entries in 6.5s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: @types/node@25.9.4 was published at 2026-06-19T07:15:05.196Z, within the minimumReleaseAge cutoff (2026-06-18T07:50:47.160Z) 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.