Background
The release executable is renamed from t3 to j5 in #414. Each macOS and Linux archive still carries a t3 -> j5 shortcut, for one reason: a server from before the rename (0.0.47 or earlier) runs a new version as t3, both for its update check from the app and for j5 update. With the shortcut, that check answers "run j5 update on the server's machine", and j5 update then installs the new version and replaces the service's launcher in one step. Nothing released after the rename looks for t3.
What to do
Remove the shortcut from the archive build (scripts/build-cli-archive.ts), the smoke check for it (scripts/smoke-cli-archive.ts), and the notes about it in FORK.md case 50 and register entry D25.
What it costs
A server still on 0.0.47 or earlier at that point can no longer update through the app or with j5 update: both fail with a generic install error, and the server keeps running. It has to be moved by hand on its machine: rerun the installer, then j5 service install. Servers that have updated at least once since the rename are unaffected.
When
When we're confident no server we care about is still on 0.0.47 or earlier. There's no technical deadline; the shortcut is one link inside each version's folder.
Agreed with Jackson, 2026-10-03.
Background
The release executable is renamed from
t3toj5in #414. Each macOS and Linux archive still carries at3 -> j5shortcut, for one reason: a server from before the rename (0.0.47 or earlier) runs a new version ast3, both for its update check from the app and forj5 update. With the shortcut, that check answers "runj5 updateon the server's machine", andj5 updatethen installs the new version and replaces the service's launcher in one step. Nothing released after the rename looks fort3.What to do
Remove the shortcut from the archive build (
scripts/build-cli-archive.ts), the smoke check for it (scripts/smoke-cli-archive.ts), and the notes about it in FORK.md case 50 and register entry D25.What it costs
A server still on 0.0.47 or earlier at that point can no longer update through the app or with
j5 update: both fail with a generic install error, and the server keeps running. It has to be moved by hand on its machine: rerun the installer, thenj5 service install. Servers that have updated at least once since the rename are unaffected.When
When we're confident no server we care about is still on 0.0.47 or earlier. There's no technical deadline; the shortcut is one link inside each version's folder.
Agreed with Jackson, 2026-10-03.