Skip to content

add preview-widget

add preview-widget #7

Triggered via push April 2, 2026 15:14
Status Failure
Total duration 39s
Artifacts –

main.yml

on: push
Compute configuration values  /  config
5s
Compute configuration values / config
Matrix: Test codebase
Lint codebase  /  lint
20s
Lint codebase / lint
Backend: Coverage  /  Test coverage with Pytest
Backend: Coverage / Test coverage with Pytest
Final report
2s
Final report
Fit to window
Zoom out
Zoom in

Annotations

34 errors and 13 warnings
Test codebase (3.12, 6.2-latest) / Tests with Pytest
Process completed with exit code 2.
Test codebase (3.12, 6.1-latest) / Tests with Pytest
Process completed with exit code 2.
Test codebase (3.12, 6.0-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.13, 6.0-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.13, 6.0-latest) / Tests with Pytest
The operation was canceled.
Test codebase (3.12, 6.0-latest) / Tests with Pytest
Process completed with exit code 2.
Test codebase (3.10, 6.0-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.10, 6.0-latest) / Tests with Pytest
Process completed with exit code 2.
Test codebase (3.13, 6.2-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.13, 6.2-latest) / Tests with Pytest
The operation was canceled.
Test codebase (3.11, 6.1-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.11, 6.1-latest) / Tests with Pytest
The operation was canceled.
Test codebase (3.11, 6.0-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.11, 6.0-latest) / Tests with Pytest
The operation was canceled.
Test codebase (3.11, 6.2-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.11, 6.2-latest) / Tests with Pytest
The operation was canceled.
Test codebase (3.10, 6.1-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.10, 6.1-latest) / Tests with Pytest
The operation was canceled.
Test codebase (3.10, 6.2-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.10, 6.2-latest) / Tests with Pytest
The operation was canceled.
Test codebase (3.13, 6.1-latest) / Tests with Pytest
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Test codebase (3.13, 6.1-latest) / Tests with Pytest
The operation was canceled.
Lint codebase / lint
Process completed with exit code 2.
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
kitconcept.seo CI
The strategy configuration was canceled because "test._3_12_6_2-latest" failed
Compute configuration values / config
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3.0.2. 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/
Test codebase (3.12, 6.2-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.12, 6.1-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.12, 6.0-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.10, 6.0-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.13, 6.2-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.11, 6.1-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.11, 6.0-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.11, 6.2-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.10, 6.1-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.10, 6.2-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Test codebase (3.13, 6.1-latest) / Tests with Pytest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/
Lint codebase / lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, astral-sh/setup-uv@v5. 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/