v2026.10.24

An AI app sign-in address for each account

24 Oct 2026 · Embed

Partners can give one account its own AI app sign-in address through the Partner API. It must sit on a website allowed for that account. If it doesn’t, the installation’s address is used.

What changed

• aiSignIn.address on Create or update an account (PUT /api/embed/v1/accounts/{accountId}). See Create or update an account.
• The address is checked when it is written and every time it is used. See Let customers sign in AI apps.
• A customer’s record in Platform shows its AI app sign-in address. See Platform screens.

When you update

Migration 117 adds one nullable column. It is expand-only, so the previous release runs on the new schema.

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:9a258fdb4dfe496eb776d97b3421f578376b54bb39937b6199c08cc2ee1ac516
docker buildx imagetools inspect ghcr.io/ralve-org/gorunner-selfhost:v2026.10.24

# Update
./deploy.sh v2026.10.24

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

Going back

• To go back, run ./deploy.sh --skip-check v2026.10.23. The older version’s check refuses the database that migration 117 changed, and --skip-check is safe here because the migration only adds.
• Going further back, below v2026.10.22, needs the OAuth rollback guard first. See v2026.10.22.