Skip to content

fix(backend): stop Gitea/Forgejo pagination on empty page response (#… #370

fix(backend): stop Gitea/Forgejo pagination on empty page response (#…

fix(backend): stop Gitea/Forgejo pagination on empty page response (#… #370

Triggered via push April 18, 2026 00:08
Status Success
Total duration 12m 25s
Artifacts 4

release-dev.yml

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

Annotations

3 warnings
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/
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/
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:07199facacfcf5da2a8693a6d842c83791617e80cd08455a107326ae3b96d70d
digests-linux-arm64 Expired
244 Bytes
sha256:eeaa09cb7f6c5f4513ff43d44fad843f7e3f379d47f065692924e0072f5e661b
sourcebot-dev~sourcebot~RCYRPV.dockerbuild
174 KB
sha256:f8617fa516b9629fdfa4bff10921a70b78c01534c7e9ff5eed7ebc41c4e0bb79
sourcebot-dev~sourcebot~XLR7VD.dockerbuild
168 KB
sha256:60f10a669adff77f0d0e0dcfd66fe8f7aa692cf0a769cc1cec39ea630c5765a1