authorgravatar for me@t3.ggTheo Browne <me@t3.gg> 2026-08-25 00:14:13-07:00
committergravatar for noreply@github.comGitHub <noreply@github.com> 2026-08-25 00:14:13-07:00
log1a4a7596c2c557fcc26a5dceefc04ac6268640b4
tree8e6d36dbdc5da951f3f9a6421b98b3949aa47620
parent43f723f807e8cc05d7fcd36ee7c3e57c9b3c4980
signature Signed by PGP key B5690EEEBB952194

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

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
188188
189189For a release smoke test, confirm `npm view t3@<version> version` returns the expected version, then
190190connect the new client to a server on the previous version and verify that the update action
191reconnects to the matching server. Use releases with identical migration manifests for the
192automatic path. When the manifest changed, verify that the remote action stops before restart and
193shows the exact local `npx t3@<version> service update` command. Also test the manual or
194desktop-managed guidance when those environments are available.
191reconnects to the matching server. When the release adds database migrations, verify that the
192remote update applies them and reconnects. A failed trial must restore the database snapshot and
193restart the previous server. If the installed launcher does not support the target protocol,
194verify that the update stops before restart and run `npx t3@<version> service update` once on the
195server machine. Also test the manual or desktop-managed guidance when those environments are
196available.
195197
196198## Desktop auto-update notes
197199