1) [chromium] › e2e/toast-under-modal.spec.ts:423:5 › toast actions under an open Radix modal (objectui#11723) › 1440 sm drawer: Undo is the click target, runs, and leaves the modal open Error: the harness did not reach "overlay open"; page errors: ["(0 , import_jsx_dev_runtime.jsxDEV) is not a function"] 308 | await wait; 309 | } catch (cause) { > 310 | throw new Error(`the harness did not reach "${what}"; page errors: ${JSON.stringify(errors)}`, { cause }); | ^ 311 | } 312 | }; 313 | await page.setViewportSize(configuration.viewport); at ready (/home/runner/work/objectui/objectui/e2e/toast-under-modal.spec.ts:310:13) at openOverlay (/home/runner/work/objectui/objectui/e2e/toast-under-modal.spec.ts:333:3) at /home/runner/work/objectui/objectui/e2e/toast-under-modal.spec.ts:424:7 [cause]: TimeoutError: page.waitForSelector: Timeout 10000ms exceeded. Call log: - waiting for locator('[role="dialog"][data-state="open"]') to be visible at openOverlay (/home/runner/work/objectui/objectui/e2e/toast-under-modal.spec.ts:333:36) at /home/runner/work/objectui/objectui/e2e/toast-under-modal.spec.ts:424:7

Process completed with exit code 2.

command (/home/runner/work/objectui/objectui/packages/cli) /usr/local/bin/pnpm run type-check exited (2)

Excessive stack depth comparing types 'Plugin & ExportedAPI' and 'Plugin'.

Process completed with exit code 1.

Error: Command failed: node /home/runner/work/objectui/objectui/scripts/check-lockfile-integrity.mjs --base-ref origin/main ::error title=Lockfile integrity::autoprefixer, nanoid, vite — see the run log; this is a lockfile regression, not a bundle regression (objectui#8326). ❯ scripts/__tests__/check-lockfile-integrity.test.ts:79:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { status: 1, signal: null, output: [ null, 'base: 5ab2f19b3f3a775c4faeeb5405809eec1bdecb5c:pnpm-lock.yaml (1773 resolutions) head: /home/runner/work/objectui/objectui/pnpm-lock.yaml (1808 resolutions)\n\n✗ autoprefixer gained a physical copy: 1 -> 2\n base autoprefixer@10.5.4(postcss@8.5.28)\n head autoprefixer@10.5.4(postcss@8.5.28)\n head autoprefixer@10.5.4(postcss@8.5.29) <- added\n\n✗ nanoid gained a physical copy: 2 -> 3\n base nanoid@3.3.18\n base nanoid@6.0.1\n head nanoid@3.3.18\n head nanoid@3.3.20 <- added\n head nanoid@6.0.1\n\n✗ vite gained a physical copy: 2 -> 3\n base vite@8.2.2(@types/node@26.2.0)(esbuild@0.27.7)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n base vite@8.2.2(@types/node@26.2.0)(esbuild@0.28.2)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n head vite@8.2.2(@types/node@26.2.0)(esbuild@0.27.7)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n head vite@8.2.2(@types/node@26.2.0)(esbuild@0.28.2)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n head vite@8.3.4(@types/node@26.2.0)(esbuild@0.28.2)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0) <- added\n\nVERDICT 3 lockfile-integrity finding(s): 0 backward move(s), 3 duplication(s).\nTwo physical copies of one package are two real paths, and nothing dedupes those — a\nbundle-size red downstream of this is caused by THIS, not by the dependency being bumped.\n⛔ This gate reports only. Re-locking from a clean base, pinning, or accepting the split\nis a decision for the pull request, not for this check.\n', '::error title=Lockfile integrity::autoprefixer, nanoid, vite — see the run log; this is a lockfile regression, not a bundle regression (objectui#8326).\n' ], pid: 3411, stdout: 'base: 5ab2f19b3f3a775c4faeeb5405809eec1bdecb5c:pnpm-lock.yaml (1773 resolutions) head: /home/runner/work/objectui/objectui/pnpm-lock.yaml (1808 resolutions)\n\n✗ autoprefixer gained a physical copy: 1 -> 2\n base autoprefixer@10.5.4(postcss@8.5.28)\n head autoprefixer@10.5.4(postcss@8.5.28)\n head autoprefixer@10.5.4(postcss@8.5.29) <- added\n\n✗ nanoid gained a physical copy: 2 -> 3\n base nanoid@3.3.18\n base nanoid@6.0.1\n head nanoid@3.3.18\n head nanoid@3.3.20 <- added\n head nanoid@6.0.1\n\n✗ vite gained a physical copy: 2 -> 3\n base vite@8.2.2(@types/node@26.2.0)(esbuild@0.27.7)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n base vite@8.2.2(@types/node@26.2.0)(esbuild@0.28.2)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n head vite@8.2.2(@types/node@26.2.0)(esbuild@0.27.7)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n head vite@8.2.2(@types/node@26.2.0)(esbuild@0.28.2)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0)\n head vite@8.3.4(@types/node@26.2.0)(esbuild@0.28.2)(jiti@2.7.0)(tsx@4.23.12)(yaml@2.9.0) <- added\n\nVERDICT 3 lockfile-integrity finding(s): 0 backward move(s), 3 duplication(s).\nTwo physical copies of one package are two real paths, and nothing dedupes those — a\nbundle-size red downstream of this is caused by THIS, not by the dependency being bumped.\n⛔ This gate reports only. Re-locking from a clean base, pinning, or accepting the split\nis a decision for the pull request, not for this check.\n', stderr: '::error title=Lockfile integrity::autoprefixer, nanoid, vite — see the run log; this is a lockfile regression, not a bundle regression (objectui#8326).\n' }

autoprefixer, nanoid, vite — see the run log; this is a lockfile regression, not a bundle regression (objectui#8326).

autoprefixer, nanoid, vite — see the run log; this is a lockfile regression, not a bundle regression (objectui#8326).

Process completed with exit code 3.

1 test shard(s) did not report success: Test (shard 7/8) (failure). ⛔ 'skipped' is not a pass here -- that is the whole reason this gate reads each shard instead of the matrix rollup (objectui#9499).

"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"

1 flaky [chromium] › e2e/toast-under-modal.spec.ts:423:5 › toast actions under an open Radix modal (objectui#11723) › 1440 sm drawer: Undo is the click target, runs, and leaves the modal open 23 skipped 41 passed (57.6s)

"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"

"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"

"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"

"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"

"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"

"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"