# v2026.10.45

One stored object for each run save

A run’s large step data is saved as one object per save, not one per value. Reading a run answers as before.

## 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:98b5089b4adfecfcded1a07f7b59a651a32b8fb3b7509165e465b4d980e7d6d2
docker buildx imagetools inspect ghcr.io/ralve-org/gorunner-selfhost:v2026.10.45

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

**Kubernetes**

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

## Going back

- To go back, run `./deploy.sh v2026.10.44`. There is no migration, so no flag is needed.
- Going back below v2026.10.44, the older version reads a step’s data saved this way as unavailable. Nothing is lost: it reads again when you update.

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