Skip to content

CI improvements

CI improvements #744

Triggered via pull request March 25, 2026 09:05
@rwb27rwb27
synchronize #293
ci-improvements
Status Success
Total duration 1m 28s
Artifacts 5

test.yml

on: pull_request
Matrix: test
base_coverage
47s
base_coverage
test-against-ofm-v3
3s
test-against-ofm-v3
test-against-ofm-feature-branch
test-against-ofm-feature-branch
Matrix: test-with-unpinned-deps
coverage
5s
coverage
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 11 warnings
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 53, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 49, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 45, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 41, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 36, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 33, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 30, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 27, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 21, Col: 7): Required property is missing: shell
test-against-ofm-v3
/home/runner/work/labthings-fastapi/labthings-fastapi/./.github/actions/test-against-ofm/action.yml (Line: 16, Col: 7): Required property is missing: shell
test-against-ofm-v3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
base_coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-with-unpinned-deps (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, barecheck/code-coverage-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-with-unpinned-deps (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-with-unpinned-deps (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-with-unpinned-deps (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-python@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
base-coverage.lcov
11.1 KB
sha256:4193e40e789c930b0f697a9300b48d088ace08db5992dd1ba714aeafd3b214f9
coverage-3.10
11.1 KB
sha256:68b283f0eb54f65984a3fe2a1ee1f615d8f41035f17552d749c309d38ed7935f
coverage-3.11
11.1 KB
sha256:68b283f0eb54f65984a3fe2a1ee1f615d8f41035f17552d749c309d38ed7935f
coverage-3.12
11.1 KB
sha256:3563b2780b49b5832f7fca6529952b6d7bff24d101cc24fbafb225f8304e6102
coverage-3.13
11.1 KB
sha256:26efc77b2df3d5a06ad60416282cf86c866c2409601bfbcf4cbd8dee49cb69d9