# v2026.10.38

One organization’s burst no longer starves the others

A burst at one workflow could queue every database connection behind its organization’s line, so every caller got `503`. Now each organization holds one connection at a time.

## What changed

## When you update

GoRunner’s image is private for now. With Docker, [sign in to the registry](https://docs.gorunner.io/self-host/install-docker#sign-in-to-the-registry) first. On Kubernetes, [sign Helm in and give the cluster its pull Secret](https://docs.gorunner.io/self-host/install-kubernetes#make-a-namespace). See [Update](https://docs.gorunner.io/self-host/update) for the whole procedure, or [Install with Docker](https://docs.gorunner.io/self-host/install-docker) and [Install on Kubernetes](https://docs.gorunner.io/self-host/install-kubernetes) to install this version anew.

**Docker**

```bash
# Check the image first: its Digest must be sha256:03c855a4f6e51d6d4e7a9c55ef32850ec562ede37ee98be18d9c03f6703369e7
docker buildx imagetools inspect ghcr.io/ralve-org/gorunner-selfhost:v2026.10.38

# Update
./deploy.sh v2026.10.38
```

**Kubernetes**

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

## Going back

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

Source: https://docs.gorunner.io/changelog/v2026.10.38