Updating your instance

RepoWrangler is self-hosted and does not auto-update. Upgrade production only to an immutable release tag such as v1.0.10; never deploy a moving main branch. Read the upgrade and rollback runbook, back up the database, and record the current tag or image digest first.

Ranch Hand Public Preview — local lifecycle

Ranch Hand's local Docker profile supports backup-first update, same-version restore, compatible rollback, repair, interrupted-operation recovery, and rollback-pool retention. Verify the desired immutable RepoWrangler release in Ranch Hand, create its bound local plan, complete preflight, and select Backup-first update. See the Ranch Hand guide.

The current Ranch Hand Public Preview does not update ACA, Cloudflare, or remote Linux deployments. Use the manual runbook below for those environments.

Build from an exact release

git fetch --tags --force
git checkout --detach vX.Y.Z

The source tree now remains pinned to that published release.

Docker Compose / local hardware

docker compose up -d --build

If your compose file uses a registry image, change it to the exact new version, pull, and restart:

docker compose pull
docker compose up -d

Node server host

pnpm install --frozen-lockfile
pnpm --filter @repo-wrangler/web build
pnpm start:server

Restart the service with the process manager used by that host.

Cloudflare Worker + D1

pnpm install --frozen-lockfile
pnpm deploy

Apply only the migrations called out by the selected release notes.

Azure Container Apps

Build and push the versioned apps/server/Dockerfile image, then apply the matching deploy/azure-container-apps template. When reapplying an existing environment, pass its custom domain and managed certificate name so the binding is preserved. Enable the in-process scheduler on exactly one replica.

Kubernetes

Roll out an image built from the release tag:

kubectl -n repo-wrangler set image deployment/repo-wrangler server=<versioned-image>
kubectl -n repo-wrangler rollout status deployment/repo-wrangler

Verify the result

• UI: inspect the vX.Y.Z under the sidebar title and About & Credits.
• API: GET /health/live must report the intended version; GET /health/ready must be ready.
• Complete sign-in, verify the custom hostname/TLS, and check Platform Health for a growing pending or failed job queue.

If verification fails, follow the rollback policy in the runbook. Application rollback is safe only when no incompatible data migration occurred or the release notes explicitly say otherwise.