1) [firefox] › src/end-to-end/shadcn/shadcn.test.ts:28:7 › Check ShadCN UI › Check link toolbar ── Error: expect(Buffer).toMatchSnapshot(expected) 209 pixels (ratio 0.01 of all image pixels) are different. Expected: /__w/BlockNote/BlockNote/tests/src/end-to-end/shadcn/shadcn.test.ts-snapshots/shadcn-link-toolbar-firefox-linux.png Received: /__w/BlockNote/BlockNote/tests/test-results/shadcn-shadcn-Check-ShadCN-UI-Check-link-toolbar-firefox/shadcn-link-toolbar-actual.png Diff: /__w/BlockNote/BlockNote/tests/test-results/shadcn-shadcn-Check-ShadCN-UI-Check-link-toolbar-firefox/shadcn-link-toolbar-diff.png 39 | 40 | await page.waitForTimeout(700); > 41 | expect(await page.screenshot()).toMatchSnapshot("shadcn-link-toolbar.png"); | ^ 42 | }); 43 | test("Check slash menu", async ({ page }) => { 44 | await focusOnEditor(page); at /__w/BlockNote/BlockNote/tests/src/end-to-end/shadcn/shadcn.test.ts:41:37

1) [chromium] › src/end-to-end/customblocks/customblocks.test.ts:24:7 › Check custom block functionality › Should be able to interactively update React custom blocks Error: expect(Buffer).toMatchSnapshot(expected) 9468 pixels (ratio 0.02 of all image pixels) are different. Expected: /__w/BlockNote/BlockNote/tests/src/end-to-end/customblocks/customblocks.test.ts-snapshots/react-interactivity-chromium-linux.png Received: /__w/BlockNote/BlockNote/tests/test-results/customblocks-customblocks--ee421--update-React-custom-blocks-chromium/react-interactivity-actual.png Diff: /__w/BlockNote/BlockNote/tests/test-results/customblocks-customblocks--ee421--update-React-custom-blocks-chromium/react-interactivity-diff.png 31 | 32 | await compareDocToSnapshot(page, "reactInteractivity"); > 33 | expect(await page.screenshot()).toMatchSnapshot("react-interactivity.png"); | ^ 34 | }); 35 | }); 36 | at /__w/BlockNote/BlockNote/tests/src/end-to-end/customblocks/customblocks.test.ts:33:37

1) [webkit] › src/end-to-end/images/images.test.ts:62:7 › Check Image Block and Toolbar functionality › Should be able to resize image Error: expect(Buffer).toMatchSnapshot(expected) 1232 pixels (ratio 0.01 of all image pixels) are different. Expected: /__w/BlockNote/BlockNote/tests/src/end-to-end/images/images.test.ts-snapshots/resize-image-webkit-linux.png Received: /__w/BlockNote/BlockNote/tests/test-results/images-images-Check-Image--cb35f-uld-be-able-to-resize-image-webkit/resize-image-actual.png Diff: /__w/BlockNote/BlockNote/tests/test-results/images-images-Check-Image--cb35f-uld-be-able-to-resize-image-webkit/resize-image-diff.png 99 | await page.waitForTimeout(500); 100 | await compareDocToSnapshot(page, "resizeImage"); > 101 | expect(await page.screenshot()).toMatchSnapshot("resize-image.png"); | ^ 102 | }); 103 | test("Should be able to delete image with backspace", async ({ page }) => { 104 | await focusOnEditor(page); at /__w/BlockNote/BlockNote/tests/src/end-to-end/images/images.test.ts:101:37

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

{ "workflowData": { "owner": "TypeCellOS", "repo": "BlockNote", "sha": "c93b4682bf061dc71ed4811dda3b7cff0140e904", "ref": "2591" }, "key": "IYTXIcvUCT", "runId": 24143410812, "webhookDebug": { "action": "requested", "head_branch": "fix/portal-floating-ui-overflow-clipping", "head_repository_full_name": "TypeCellOS/BlockNote", "full_name": "TypeCellOS/BlockNote", "isPullRequest": true, "prNumber": 2591, "prNumberType": "number", "isNewPullRequest": true, "isOldPullRequest": false, "prKey": "TypeCellOS/BlockNote:fix/portal-floating-ui-overflow-clipping", "oldPrDataHash": "rzu8DCz43M", "lookupKey": "TypeCellOS/BlockNote:fix/portal-floating-ui-overflow-clipping", "data": { "owner": "TypeCellOS", "repo": "BlockNote", "sha": "c93b4682bf061dc71ed4811dda3b7cff0140e904", "ref": "2591" } } }

1 flaky [firefox] › src/end-to-end/shadcn/shadcn.test.ts:28:7 › Check ShadCN UI › Check link toolbar ─── 39 passed (47.6s)

40 passed (34.7s)

40 passed (1.0m)

1 flaky [chromium] › src/end-to-end/customblocks/customblocks.test.ts:24:7 › Check custom block functionality › Should be able to interactively update React custom blocks 2 skipped 81 passed (1.2m)

12 skipped 72 passed (1.4m)