Skip to content

Drafting new release #171

Drafting new release

Drafting new release #171

Triggered via pull request May 5, 2026 20:28
@iu2frliu2frl
ready_for_review #77
dev
Status Success
Total duration 8m 0s
Artifacts 6

ci.yml

on: pull_request
Unit Tests  /  Backend unit tests (pytest)
7m 55s
Unit Tests / Backend unit tests (pytest)
Frontend Tests  /  Frontend unit tests (Vitest)
49s
Frontend Tests / Frontend unit tests (Vitest)
Integration Tests  /  Backend CRUD smoke tests
59s
Integration Tests / Backend CRUD smoke tests
Docker Build  /  Build Docker images and smoke-test stack
1m 46s
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
218 KB
sha256:153697b2761cd78a10dae08fee91b44ff1bfa015e22e781e8bdf62d93bbabe55
frontend-coverage-node20 Expired
216 KB
sha256:793a59045c7e8b85d1b74168989360fccfad12d2030627ff68465ea650cbe4cb
frontend-junit-results-node20 Expired
11.6 KB
sha256:e8d5e4c80a9bf106e114519f3275a211bd80eeb1200e7d419ff1788fe627724f
iu2frl~CloudShell~AVLAYZ.dockerbuild Expired
36 KB
sha256:019eafab2980080fe5c9123b6b77d6d0c82cb169bed6b567e06244733e9701ab
iu2frl~CloudShell~QMSCJJ.dockerbuild Expired
46.8 KB
sha256:bfd0af5d50c8e0f370fe1874bc8180eedf3c6b3c3cf9a513f1223d63c48fe1bb
junit-results-py3.12 Expired
8.65 KB
sha256:ba2094216a6026e95890150209ab1023f3eb7a84d268ad62b54e229898d492af