Skip to content

chore: update GO_VERSION to 1.26 in keploy-ci Dockerfile (#12) #32

chore: update GO_VERSION to 1.26 in keploy-ci Dockerfile (#12)

chore: update GO_VERSION to 1.26 in keploy-ci Dockerfile (#12) #32

Triggered via push March 11, 2026 11:16
Status Failure
Total duration 4m 24s
Artifacts 11

docker-build.yml

on: push
Matrix: base-images
Matrix: derived-images
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 11 warnings
base (amd64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux; ARCH=\"${TARGETARCH:-$(dpkg --print-architecture)}\"; case \"$ARCH\" in amd64|arm64) ;; *) echo \"Unsupported architecture: $ARCH\"; exit 1 ;; esac; curl -fsSL \"https://go.dev/dl/go${GO_VERSION}.linux-${ARCH}.tar.gz\" -o /tmp/go.tgz; rm -rf /usr/local/go; tar -C /usr/local -xzf /tmp/go.tgz; rm -f /tmp/go.tgz" did not complete successfully: exit code: 22
base (arm64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c set -eux; ARCH=\"${TARGETARCH:-$(dpkg --print-architecture)}\"; case \"$ARCH\" in amd64|arm64) ;; *) echo \"Unsupported architecture: $ARCH\"; exit 1 ;; esac; curl -fsSL \"https://go.dev/dl/go${GO_VERSION}.linux-${ARCH}.tar.gz\" -o /tmp/go.tgz; rm -rf /usr/local/go; tar -C /usr/local -xzf /tmp/go.tgz; rm -f /tmp/go.tgz" did not complete successfully: exit code: 22
slim- (amd64)
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. 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/
timefreeze- (amd64)
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. 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/
slim- (arm64)
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, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
awscli- (amd64)
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. 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/
golint- (amd64)
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. 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/
go-build- (amd64)
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. 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/
base (amd64)
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. 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/
golint- (arm64)
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, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
timefreeze- (arm64)
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, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
awscli- (arm64)
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, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
base (arm64)
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, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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
keploy~docker-images~53PDHA.dockerbuild
30.7 KB
sha256:1657d35c0f8589cf21e6d31e7afbcc946ab18b7af10d0ed5331a28d21a12acb0
keploy~docker-images~83NB4V.dockerbuild
38.2 KB
sha256:1c8727630635f00b20ccf990d6aa73e6ede4fb886f7d12eb883e6d041f37ec76
keploy~docker-images~CSXJL9.dockerbuild
34.3 KB
sha256:5de0e7d32ab8d5a0f115e337b6cacbe5386a19da228e0016c602673ae6c92eca
keploy~docker-images~ETN5QK.dockerbuild
40.8 KB
sha256:ddb7cfb018134bff20c2f2a37d13009703c93fc340ca27cfe4ffe2c9c6ad04bb
keploy~docker-images~H6Z4CU.dockerbuild
40.4 KB
sha256:b4ce75a5314e02a3a14eb0ba98ced4a45278587ad03535b01c55e9c492792a6a
keploy~docker-images~JFPGLM.dockerbuild
26.9 KB
sha256:79f994d37a14b8246a28daf34131bf690dd4e8d33f13bf32e1354328888f0ddf
keploy~docker-images~JGYZD9.dockerbuild
26.2 KB
sha256:56bf07ed95b77e832612252c338bd049309f0fcd77a516ffdd4446fbb63e6389
keploy~docker-images~RQ7IJ2.dockerbuild
41 KB
sha256:031ead675ed711f3b020c582ad481f0fb55dec445632ba075bbc7ad69fce925d
keploy~docker-images~TNSPLA.dockerbuild
37.3 KB
sha256:b889cec74dd570a71ab0f17b131f3dd372b9a30e29f3d7510fa90a92f2f1f882
keploy~docker-images~XB211U.dockerbuild
33.4 KB
sha256:6bfe24078a448c03611c4aaeef8d79de4a4b2ab6ab5690c679249db8d94a2fcb
keploy~docker-images~YV3NZD.dockerbuild
31.2 KB
sha256:5d00bd4edec48cf9629334af306f35f22c830e9a0a1a116e9d18bf37debcffd8