Skip to content
Backend Image Pipeline

ci: force staging caddy bind to loopback #13

Sign in to view logs

ci: force staging caddy bind to loopback

ci: force staging caddy bind to loopback #13

Triggered via push May 11, 2026 08:58
@nedasvinedasvi
pushed e4305cc
main
Status Success
Total duration 4m 32s
Artifacts 3

publish-images.yml

on: push
Matrix: Build and publish images
Deploy to production
0s
Deploy to production
Deploy to staging
1m 49s
Deploy to staging
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Build and publish images (dashboard, ./dashboard/Dockerfile, ./dashboard, resolvekit-dashboard, N...
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. 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 publish images (backend, ./Dockerfile, ., resolvekit-backend)
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. 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 publish images (kb-service, ./knowledge_bases/Dockerfile, ., resolvekit-kb-service)
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. 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
resolve-kit~resolvekit-backend~8M7LU1.dockerbuild Expired
78.8 KB
sha256:7608e3c658dd0f43ea18c74d9e4c2b7952f8ec1d9fe23183e5b907d80395bfb2
resolve-kit~resolvekit-backend~OY49BA.dockerbuild Expired
66.8 KB
sha256:90ac75514ab955b96d95303d6eda8561dc728d98e72c7847b7dd580c134cfbb7
resolve-kit~resolvekit-backend~P86RRI.dockerbuild Expired
41 KB
sha256:3edc503229813a576e146805b40abeca928aff943423eab9abd0e5fcc2462165