Skip to content
Publish GHCR Images

fix: rename cache key for tree details builds to avoid key collision … #55

Sign in to view logs

fix: rename cache key for tree details builds to avoid key collision …

fix: rename cache key for tree details builds to avoid key collision … #55

Triggered via push April 13, 2026 12:35
@github-merge-queuegithub-merge-queue[bot]
pushed 9af36b8
main
Status Success
Total duration 1m 17s
Artifacts 3

deploy-containers.yaml

on: push
build-and-push-backend
1m 4s
build-and-push-backend
build-and-push-dashboard
1m 6s
build-and-push-dashboard
build-and-push-proxy
21s
build-and-push-proxy
verify
3s
verify
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build-and-push-proxy
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/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/
build-and-push-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@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/
build-and-push-dashboard
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/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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: dashboard/Dockerfile#L22
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Artifacts

Produced during runtime
Name Size Digest
kernelci~dashboard~2ZWTPO.dockerbuild
38.7 KB
sha256:f202692ff7640c2fa219f8914a7b638f2531320758fd76a151e87a5b289dedef
kernelci~dashboard~3GN7WC.dockerbuild
46.3 KB
sha256:d464a8b8ba6205204c56969c23c8da1aefc077cb71c64f7a88ed1925a4040ccf
kernelci~dashboard~8OQN65.dockerbuild
53.1 KB
sha256:8f34159087843a04b56e60b45706e45f840e6da422d8a85574318ca658b493cd