Commit 1a4a7596c2c557fcc26a5dceefc04ac6268640b4 | the-knife

1 files changed, 6 insertions(+), 4 deletions(-)

docs/operations/release.md+6-4

 @@ -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
+reconnects to the matching server. When the release adds database migrations, verify that the
-automatic path. When the manifest changed, verify that the remote action stops before restart and
+remote update applies them and reconnects. A failed trial must restore the database snapshot and
-shows the exact local `npx t3@<version> service update` command. Also test the manual or
+restart the previous server. If the installed launcher does not support the target protocol,
-desktop-managed guidance when those environments are available.
+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