Skip to content

CI improvements

CI improvements #743

Triggered via pull request March 24, 2026 22:12
@rwb27rwb27
synchronize #293
ci-improvements
Status Success
Total duration 1m 26s
Artifacts 5

test.yml

on: pull_request
Matrix: test
base_coverage
49s
base_coverage
test-against-ofm-v3
3s
test-against-ofm-v3
test-against-ofm-feature-branch
0s
test-against-ofm-feature-branch
Matrix: test-with-unpinned-deps
coverage
6s
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.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 (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-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/
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.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/
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/
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/

Artifacts

Produced during runtime
Name Size Digest
base-coverage.lcov
11.1 KB
sha256:7080dfc98034b514c079eb9de2ea8609edc3d19dd21ddd7dcc91fdddd0e8aae3
coverage-3.10
11.1 KB
sha256:3dc829b249855e8cec87886fd732153ddf88a9a65d5ea373ba77a7a3ac81a253
coverage-3.11
11.1 KB
sha256:b1f37da343b8cf83df9e1bf2e98db4d44d6809431e0ed2cea6516a7764c63d0c
coverage-3.12
11.1 KB
sha256:9eb81a1e4e251d1e0a6a9c0824482e7e87c087ba4f21604bf10294deb593071f
coverage-3.13
11.1 KB
sha256:b1f37da343b8cf83df9e1bf2e98db4d44d6809431e0ed2cea6516a7764c63d0c