Skip to content

chore(deps): bump google.golang.org/grpc (#212) #357

chore(deps): bump google.golang.org/grpc (#212)

chore(deps): bump google.golang.org/grpc (#212) #357

Triggered via push March 19, 2026 07:11
Status Failure
Total duration 7m 41s
Artifacts 4

build-image.yaml

on: push
Matrix: Build a Docker image
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Build a Docker image (linux/arm)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c go mod download" did not complete successfully: exit code: 1
Build a Docker image (linux/amd64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c go mod download" did not complete successfully: exit code: 1
Build a Docker image (linux/arm64)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c go mod download" did not complete successfully: exit code: 1
Build a Docker image (linux/arm64/v8)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c go mod download" did not complete successfully: exit code: 1
Build a Docker image (linux/arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, reproducible-containers/buildkit-cache-dance@v3.3.2. 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/
Build a Docker image (linux/amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, reproducible-containers/buildkit-cache-dance@v3.3.2. 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/
Build a Docker image (linux/arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, reproducible-containers/buildkit-cache-dance@v3.3.2. 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/
Build a Docker image (linux/arm64/v8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3, reproducible-containers/buildkit-cache-dance@v3.3.2. 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
ChargePi~ChargePi-go~5F5J8A.dockerbuild Expired
69.6 KB
sha256:7add61b029c7fc41ccd566cac890559a92d75286ccdfab095550899c082f99ab
ChargePi~ChargePi-go~JHJA4Z.dockerbuild Expired
44.8 KB
sha256:10fda2201fcdbef10ee1cbf5b5b60fee48c844884b09999a83ebf73a2ffc9fc4
ChargePi~ChargePi-go~OCRT7A.dockerbuild Expired
71.4 KB
sha256:1102e72d13c75eb99fdb1f126e3d1d4f5ab58b8a06ed6bb42c38e66e7a0b15a7
ChargePi~ChargePi-go~XPEF69.dockerbuild Expired
70 KB
sha256:317051d565eee4652f25d93dd1cde195ae216da9900f9366ea866e2475ebd225