Skip to content

fix: correct field types across models, migrations, and frontend #93

fix: correct field types across models, migrations, and frontend

fix: correct field types across models, migrations, and frontend #93

Triggered via push March 26, 2026 11:51
Status Success
Total duration 2m 14s
Artifacts 2

main.yaml

on: push
build-frontend
1m 59s
build-frontend
build-backend
50s
build-backend
notify-watchtower
8s
notify-watchtower
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build-backend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v6, docker/login-action@v3, 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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L2
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
build-frontend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v6, docker/login-action@v3, 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/

Artifacts

Produced during runtime
Name Size Digest
KSET~brucifer-karte-2022~SMR82T.dockerbuild
54.7 KB
sha256:0c0ad18893f00ad35bb2405feafabf35eed4f5e3580297e78b9c64d505d4a068
KSET~brucifer-karte-2022~ZJFVU9.dockerbuild
60.2 KB
sha256:36ce5bd97994dd4c7d610340d404906f06471a502cfb5f142ecba70fb567a8c0