Skip to content

test(backend): fix repoCompileUtils tests broken by fs.stat directory… #295

test(backend): fix repoCompileUtils tests broken by fs.stat directory…

test(backend): fix repoCompileUtils tests broken by fs.stat directory… #295

Triggered via push March 26, 2026 06:28
Status Success
Total duration 12m 36s
Artifacts 4

release-dev.yml

on: push
Matrix: build / build
publish-to-registry  /  merge
18s
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. 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:1ccfdc946dd45698f4a16e0b3a75b1c1e6700cf82b0b9c7f9ca99f8662caf03f
digests-linux-arm64 Expired
244 Bytes
sha256:5fc76a55a923619c89861f70285407edd76ca1514ec09431ca9313ebe1b2eb10
sourcebot-dev~sourcebot~KQVCPK.dockerbuild
168 KB
sha256:3c9ec62e5a59f8ab37a2aa838546e7a68ad3b373c7af7b0d0ba9cde8c12463d7
sourcebot-dev~sourcebot~PZVTPM.dockerbuild
171 KB
sha256:edfd1d28abb3494de0e4ea5a0185f07d926fd8d96df4ac5c2bbceeb9f2b12523