Skip to content

Open-source Grok Bot alternative for named AI teammates. Local-first desktop, web, and mobile clients with per-bot tools, instructions, and memory. Independent fork of T3 Code.

docs(release): verify remote updates with database migrations (#8177)

Theo Browne1a4a7596c2c5
diff --git a/docs/operations/release.md b/docs/operations/release.md
index 520af51d9..68f2e8da5 100644
--- a/docs/operations/release.md
+++ b/docs/operations/release.md
@@ -188,10 +188,12 @@ the **Update server** action targeting a package version that does not exist yet
For a release smoke test, confirm `npm view t3@<version> version` returns the expected version, then
connect the new client to a server on the previous version and verify that the update action
-reconnects to the matching server. Use releases with identical migration manifests for the
-automatic path. When the manifest changed, verify that the remote action stops before restart and
-shows the exact local `npx t3@<version> service update` command. Also test the manual or
-desktop-managed guidance when those environments are available.
+reconnects to the matching server. When the release adds database migrations, verify that the
+remote update applies them and reconnects. A failed trial must restore the database snapshot and
+restart the previous server. If the installed launcher does not support the target protocol,
+verify that the update stops before restart and run `npx t3@<version> service update` once on the
+server machine. Also test the manual or desktop-managed guidance when those environments are
+available.
## Desktop auto-update notes