Skip to content

feat: replace domain conditions with standard Ready/Progressing condi… #18

feat: replace domain conditions with standard Ready/Progressing condi…

feat: replace domain conditions with standard Ready/Progressing condi… #18

Triggered via push March 25, 2026 18:53
Status Failure
Total duration 29s
Artifacts
publish-image
25s
publish-image
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
publish-image
Error response from daemon: Get "https://registry-1.docker.io/v2/": received unexpected HTTP status: 500 Internal Server Error
publish-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@fac708d6674e30b6ba41289acaab6d4b75aa0753, docker/login-action@465a07811f14bebb1938fbed4728c6a1ff8901fc, docker/setup-buildx-action@f95db51fddba0c2d1ec667646a06c2ce06100226. 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/
publish-image
Failed to restore: Cache service responded with 400