Skip to content

fix: correct platform handling and tag formatting in Docker build wor… #129

fix: correct platform handling and tag formatting in Docker build wor…

fix: correct platform handling and tag formatting in Docker build wor… #129

Triggered via push March 30, 2026 03:14
Status Failure
Total duration 2m 6s
Artifacts 2

ci-cd.yaml

on: push
cache  /  build-cache
9s
cache / build-cache
test  /  unit-test-coverage
12s
test / unit-test-coverage
Matrix: docker-build-and-image-scan / build
docker-build-and-image-scan  /  manifest
docker-build-and-image-scan / manifest
release  /  Semantic-Release
release / Semantic-Release
Matrix: release / Docker-Release / build
Waiting for pending jobs
release  /  ...  /  manifest
release / Docker-Release / manifest
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
docker-build-and-image-scan / build (linux/arm64, linux-arm64)
Process completed with exit code 1.
cache / build-cache
Cache save failed.
lint / ruff-lint
Cache save failed.
test / unit-test-coverage
Cache save failed.
docker-build-and-image-scan / build (linux/amd64, linux-amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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-and-image-scan / build (linux/arm64, linux-arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. 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
milsman2~python-app-template~RVU7DL.dockerbuild Expired
50.1 KB
sha256:0636d6ec0ccbf5c864f74018e808df5fb96422ff51da2b5214a74a6991de570a
milsman2~python-app-template~S3S4KN.dockerbuild Expired
57.2 KB
sha256:9d5ab69f98f8e8d280c5075b5efaeb9996d3b52e60cb11e2657937226ebdc44d