Skip to content

Commit 1bb2504

Browse files
docs(relay): require the client update message before legacy cleanup
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 292c3f0 commit 1bb2504

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

‎docs/operations/release.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,9 @@ A deleted legacy tunnel keeps its allocation, so its hostname is kept. When the
216216
2. Set the legacy mode to `dry-run`, deploy, and read `wouldDeleteLegacy`, `legacyOver30Days`,
217217
`totalDown`, and `totalInactive` on the sweep spans for a day.
218218
3. Run the legacy steps of the disposable-host canary below.
219-
4. Set the legacy mode to `enabled`. One sweep deletes at most 100 tunnels, so a backlog of
219+
4. Before enabling, confirm the web and mobile builds that show the "update T3 Code on that computer"
220+
message are live. Without them, a user whose older host lost its tunnel only sees it as offline.
221+
5. Set the legacy mode to `enabled`. One sweep deletes at most 100 tunnels, so a backlog of
220222
20,000 takes about 17 hours. Watch `deletedLegacy`, `failed`, and `truncated`.
221223

222224
### Disposable-host canary

0 commit comments

Comments
 (0)