GoRunner docs
Search or askSearch⌘K

v2026.10.58

Database columns nothing read are gone

31 Oct 2026 · Cloud · Self-hosted · Embed

This release removes 18 database columns that nothing reads. On Cloud nothing changes, and on every edition runs and API answers stay as they were. A self-hosted or embedded installation must pass through v2026.10.57 on the way here, and can’t go back below it afterwards.

What changed

When you update

Warning Once this version has run, the installation can’t go back below v2026.10.57, except from a backup.

Before you update

  1. Update to v2026.10.57 and let it finish. Straight across from an older version, the older containers can’t read the database until each one is replaced: the API answers 500, and workers’ saves fail and are retried. See Update.
  2. Back up the database and the files. It is the only way back below v2026.10.57. See Back up and restore.

During the update

  • If a long-running query holds a table, the update can stop at Applying migrations, with the old version still running. Run the same command again.
  • A query of your own on GoRunner’s database stops working if it names a removed column: platform_id on connections, folders, workflows and workflow_runs; connections.key_version; plan, settings, branding_override and stripe_customer_id on organizations; workspaces.settings; users.avatar_url; org_id and workspace_id on step_runs; and custom_domain, branding, settings, stripe_customer_id and dek_wrapped on platforms.

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:25af3c68038ddad0855e20807ae4e252208097161ced550954c3432476ff2e5a
docker buildx imagetools inspect ghcr.io/ralve-org/gorunner-selfhost:v2026.10.58

# Update
./deploy.sh v2026.10.58

Going back

Warning Below v2026.10.57 there is no way back but the backup. Older versions fail on sign-in, organizations and workspaces, and can’t save a run’s steps. Their check may still offer --skip-check, and helm rollback doesn’t stop you: use neither.

To go back to v2026.10.57, run ./deploy.sh --skip-check v2026.10.57. Its check refuses the database this version changed, and --skip-check is safe here because v2026.10.57 doesn’t use the removed columns.