Skip to content

fix: Apply property filter max width only to filtering input #4811

fix: Apply property filter max width only to filtering input

fix: Apply property filter max width only to filtering input #4811

Triggered via push October 10, 2024 07:37
Status Cancelled
Total duration 4m 16s
Artifacts

release.yml

on: push
Matrix: Components a11y tests
Components unit tests
4m 2s
Components unit tests
Components integ tests
4m 5s
Components integ tests
release  /  release
release / release
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 2 warnings
Components a11y tests (5)
The run was canceled by @gethinwebster.
Components a11y tests (5)
The operation was canceled.
Components unit tests
The run was canceled by @gethinwebster.
Components unit tests
The operation was canceled.
Components a11y tests (3)
The run was canceled by @gethinwebster.
Components a11y tests (3)
The operation was canceled.
Components a11y tests (2)
The run was canceled by @gethinwebster.
Components a11y tests (2)
The operation was canceled.
Components a11y tests (6)
The run was canceled by @gethinwebster.
Components a11y tests (6)
The operation was canceled.
Components integ tests
The run was canceled by @gethinwebster.
Components integ tests
The operation was canceled.
Components a11y tests (1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Components a11y tests (4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/