Skip to content

fix(web): restore ServiceError boundary in getFileSourceForRepo (#1… #396

fix(web): restore ServiceError boundary in getFileSourceForRepo (#1…

fix(web): restore ServiceError boundary in getFileSourceForRepo (#1… #396

Triggered via push April 23, 2026 18:04
Status Success
Total duration 12m 12s
Artifacts 4

release-dev.yml

on: push
Matrix: build / build
publish-to-registry  /  merge
17s
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:e1b6653f7c9bb4eebfbed26f3a3a456396d3119f68a1946147b2f373f95ca82e
digests-linux-arm64 Expired
244 Bytes
sha256:9825c55ad4803ee0365a19cc7e88b033ee990c8534518ce64ab0a0a0e6c9e6ed
sourcebot-dev~sourcebot~IYHCGH.dockerbuild
170 KB
sha256:ad53b135ec0e81d453c2ece697cf13e24c26598cd5596ff5ef0620f848baac5e
sourcebot-dev~sourcebot~QRNDP3.dockerbuild
175 KB
sha256:2916f8ebbc892f8ad85b407136245f8f93dfba7032e9a5d1498c3e37d75d41e6