Process completed with exit code 1.

@mendix/datagrid-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)

datagrid-web filtering integration: Error: expect(page).toHaveScreenshot(expected) failed 101 pixels (ratio 0.01 of all image pixels) are different. Snapshot: datagridFilteringIntegration.png Call log: - Expect "toHaveScreenshot(datagridFilteringIntegration.png)" with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 101 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 101 pixels (ratio 0.01 of all image pixels) are different. - Error: expect(page).toHaveScreenshot(expected) failed 101 pixels (ratio 0.01 of all image pixels) are different. Snapshot: datagridFilteringIntegration.png Call log: - Expect "toHaveScreenshot(datagridFilteringIntegration.png)" with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 101 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 101 pixels (ratio 0.01 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-web/e2e/filtering/DataGridFilteringIntegration.spec.js:55:24

compares with a screenshot baseline and checks datagrid using virtual scrolling are rendered as expected: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-page') 110 pixels (ratio 0.01 of all image pixels) are different. Snapshot: datagrid-virtual-scrolling.png Call log: - Expect "toHaveScreenshot(datagrid-virtual-scrolling.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-page') - locator resolved to <div data-focusindex="0" class="mx-page layout-atlas layout-atlas-responsive-default">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 110 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-page') - locator resolved to <div data-focusindex="0" class="mx-page layout-atlas layout-atlas-responsive-default">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 110 pixels (ratio 0.01 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-page') 110 pixels (ratio 0.01 of all image pixels) are different. Snapshot: datagrid-virtual-scrolling.png Call log: - Expect "toHaveScreenshot(datagrid-virtual-scrolling.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-page') - locator resolved to <div data-focusindex="0" class="mx-page layout-atlas layout-atlas-responsive-default">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 110 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-page') - locator resolved to <div data-focusindex="0" class="mx-page layout-atlas layout-atlas-responsive-default">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 110 pixels (ratio 0.01 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-web/e2e/DataGrid.spec.js:194:48

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

`../typings/CellComponent` import should occur after import of `./CellElement`

`@mendix/widget-plugin-grid/keyboard-navigation/useFocusTargetProps` import should occur after import of `react`

`react` import should occur before import of `@mendix/widget-plugin-hooks/useEventCallback`

`@mendix/widget-plugin-mobx-kit/react/useConst` import should occur after import of `react`

`react` import should occur before import of `@mendix/widget-plugin-component-kit/If`

`mobx-react-lite` import should occur before import of `@mendix/widget-plugin-component-kit/If`

`../model/hooks/injection-hooks` import should occur after import of `./CellElement`

`@mendix/widget-plugin-grid/keyboard-navigation/useFocusTargetProps` import should occur after import of `react`

`@mendix/widget-plugin-grid/components/Pagination` import should occur after import of `typings/DatagridProps`

`@mendix/widget-plugin-component-kit/If` import should occur after import of `typings/DatagridProps`

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/