Skip to content

Implementing #63 (#73) #154

Implementing #63 (#73)

Implementing #63 (#73) #154

Triggered via push April 29, 2026 16:01
Status Success
Total duration 7m 52s
Artifacts 6

ci.yml

on: push
Unit Tests  /  Backend unit tests (pytest)
7m 40s
Unit Tests / Backend unit tests (pytest)
Frontend Tests  /  Frontend unit tests (Vitest)
38s
Frontend Tests / Frontend unit tests (Vitest)
Integration Tests  /  Backend CRUD smoke tests
52s
Integration Tests / Backend CRUD smoke tests
Docker Build  /  Build Docker images and smoke-test stack
2m 14s
Docker Build / Build Docker images and smoke-test stack
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Frontend Tests / Frontend unit tests (Vitest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. 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/
Integration Tests / Backend CRUD smoke tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/setup-python@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/
Docker Build / Build Docker images and smoke-test stack
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.backend#L36
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TOKEN_TTL_HOURS") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Unit Tests / Backend unit tests (pytest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5, actions/upload-artifact@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
coverage-report-py3.12 Expired
208 KB
sha256:20f2d31932a2e3d5c584f6423d096c400897cc47ef2a0548684fc554035a848b
frontend-coverage-node20 Expired
213 KB
sha256:b0e5e2975c1f61ff077a57999f9f281eabd2f100fdcbe0d41712df21044efaac
frontend-junit-results-node20 Expired
12 KB
sha256:1d74281e0c71acae5b03ea5bae0fa3fcbe4b0ec185a1990b1570b82c5b0f07f9
iu2frl~CloudShell~73K5NI.dockerbuild Expired
50.9 KB
sha256:a47d4176a32448318164ade6a6ae3b96832c365d6cbf50bbdcff7289ecbdbfb9
iu2frl~CloudShell~NC0D10.dockerbuild Expired
49.9 KB
sha256:c22bf4767d257f8c1c000a3085a6c33a3b035754cc0ee77caabbebb659b723d2
junit-results-py3.12 Expired
8.51 KB
sha256:495a8e8f46594f6b2cbcdffb05f0479df720aeff5fea4f491bafebbbdf312045