Skip to content

Implementing #63 (#73) (#74) #157

Implementing #63 (#73) (#74)

Implementing #63 (#73) (#74) #157

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

ci.yml

on: push
Unit Tests  /  Backend unit tests (pytest)
7m 39s
Unit Tests / Backend unit tests (pytest)
Frontend Tests  /  Frontend unit tests (Vitest)
43s
Frontend Tests / Frontend unit tests (Vitest)
Integration Tests  /  Backend CRUD smoke tests
55s
Integration Tests / Backend CRUD smoke tests
Docker Build  /  Build Docker images and smoke-test stack
1m 37s
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:af1a5bac06f7e9995d20f970f17f114024a02380562236adee8d865d07bf5006
frontend-coverage-node20 Expired
213 KB
sha256:f1d2f4b0bf847e8e80dd6c5f12a494b9142595ea26bbbbdda22cf56e290a1bea
frontend-junit-results-node20 Expired
12 KB
sha256:0b8b1107acaeff7510cd3da3c57c1cc24d45cc5ab274a505353882d4ecfde1e7
iu2frl~CloudShell~50YN4A.dockerbuild Expired
50.1 KB
sha256:a19177453bdeb5de9a436ae46dd7bf53a7e8741f5204cc5bb5e35a650ad44f3a
iu2frl~CloudShell~W5HTWK.dockerbuild Expired
50.3 KB
sha256:fc21d115dd83a687b3d13970c69dd6f7d72fc531e826dc3f56fc3e7cce0e77c1
junit-results-py3.12 Expired
8.44 KB
sha256:aaa7317810529dbd6adf140884ea4d47bc5fc85e93369a1e1fd78c732afe936b