Skip to content
Docker Image CI/CD

fix: add yaml dependency and update fail-fast strategy in CI workflow #38

Sign in to view logs

fix: add yaml dependency and update fail-fast strategy in CI workflow

fix: add yaml dependency and update fail-fast strategy in CI workflow #38

Triggered via push May 12, 2026 08:33
@mjanezmjanez
pushed ebfc9f2
develop
Status Cancelled
Total duration 6h 7m 3s
Artifacts 2

docker-publish.yml

on: push
Matrix: Test Docker Build
Build and Push Backend to GHCR
2m 35s
Build and Push Backend to GHCR
Build and Push Frontend to GHCR
6h 5m
Build and Push Frontend to GHCR
Comment on PR
Comment on PR
Matrix: Security Scan
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Build and Push Frontend to GHCR
The job has exceeded the maximum execution time of 6h0m0s
Test Docker 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@v4, docker/build-push-action@v5, 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/
Test Docker 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@v4, docker/build-push-action@v5, 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/
Build and Push Backend to GHCR
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@36fa7d009e22618ca7cd599486979b8150596c74, actions/attest@67422f5511b7ff725f4dbd6fb9bd2cd925c65a8d, actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-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
mjanez-metadata-quality-react-backend_sha256_08b93f2fa0474ba3b2cd0a8223d12ee992d6e99b5e7219209a2640fee0f00685.spdx.json
574 KB
sha256:7226f6c3bd0836388c233b835f62b3e8027c5c426ae35a279fb48a213eb0c6b6
sbom-backend
574 KB
sha256:7c53b29af325d7235fecb69cdd328d99da5ed55d580235f296a9ddc6bd71bea7