Skip to content

feat: add Coastfile for local development (#1058) #338

feat: add Coastfile for local development (#1058)

feat: add Coastfile for local development (#1058) #338

Triggered via push April 13, 2026 16:27
Status Success
Total duration 12m 44s
Artifacts 4

release-dev.yml

on: push
Matrix: build / build
publish-to-registry  /  merge
24s
publish-to-registry / merge
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
build / build (linux/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, actions/upload-artifact@v4, 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 / build (linux/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, actions/upload-artifact@v4, 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/
publish-to-registry / merge
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, 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
digests-linux-amd64 Expired
244 Bytes
sha256:34f2813acd61e62c66a9da7a51acaa4872063f89ee787083c16a8d0befb61834
digests-linux-arm64 Expired
244 Bytes
sha256:9532d95fa6f1ca1579bccd4d5f7b73c65ffdc229b9edc4c03ae80c012e119159
sourcebot-dev~sourcebot~O2LKQ9.dockerbuild
167 KB
sha256:5fd657f6aa760a512f50836ff5fb95a6cd12f81c86a63ea0fa81731eaa5fba8d
sourcebot-dev~sourcebot~ZIPA2Q.dockerbuild
167 KB
sha256:6a9fdf579260ac40900d0d9c11172e93a08a4a946a099cf86ae534d9a1ca3ece