v2026.10.54

A busy server says so

30 Oct 2026 · Cloud · Self-hosted · Embed

When a server holds as much request data as it can, a call now waits up to 2 seconds and then answers 503 BUSY with Retry-After, before anything is done. A run waits for room in the Code sandbox before it starts.

What changed

• A new answer, 503 BUSY, for a body that doesn’t fit in the server’s in-flight budget, and for a read of a run’s large data. See BUSY.

When you update

GoRunner’s image is private for now. With Docker, sign in to the registry first. On Kubernetes, sign Helm in and give the cluster its pull Secret. See Update for the whole procedure, or Install with Docker and Install on Kubernetes to install this version anew.

# Check the image first: its Digest must be sha256:58cb2512820dce5ebee17db799d8ac2649741d07670e6df189e7bfec03992f91
docker buildx imagetools inspect ghcr.io/ralve-org/gorunner-selfhost:v2026.10.54

# Update
./deploy.sh v2026.10.54

helm upgrade gorunner oci://ghcr.io/ralve-org/charts/gorunner --version 2026.10.54 -f values.yaml

Going back

To go back, run ./deploy.sh v2026.10.53. There is no migration, so no flag is needed.