DodoTech-Public/DodoSSH
Public Access
2
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases 2 Wiki Activity

Merge branch 'claude/android-release'
ci / build and test (push) Successful in 1m57s
Details
ci / android head (push) Successful in 3m13s
Details
ci / desktop nightly (push) Successful in 41s
Details
ci / api image (push) Successful in 23s
Details

Browse Source
This commit is contained in:
jaap-jan
2026-08-05 22:49:51 +02:00
parent 8591035170 af0e29a98b
commit 174ef7c420
16 changed files with 712 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/manual-checks.md
+23
View File
@@ -2005,6 +2005,29 @@ is wrong. Reinstalling then asks for the passphrase rather than for a server.
lost their offline unlock and any change that was still in the outbox. That is the failure ADR 0013
decision 2 exists to prevent, and it is why 16.1 checks the same thing from the other end.
### 16.10 The nightly installs beside the release build and not over it · **the one CI cannot check**
Needs both: a release build installed by walking 16.1, and `DodoSSH.Desktop.Nightly-win-nightly-Setup.exe`
from the `nightly-desktop` release. Install the nightly second, and then start **both**.
**Pass:** two entries in the Start menu, one *DodoSSH* and one *DodoSSH Nightly*; two directories,
`%LOCALAPPDATA%\DodoSSH.Desktop` and `%LOCALAPPDATA%\DodoSSH.Desktop.Nightly`; two profiles,
`%LOCALAPPDATA%\DodoSSH` and `%LOCALAPPDATA%\DodoSSH.Nightly`, each with its own `cache.db` and
`device.key`. The nightly's titlebar says **DodoSSH Nightly** and the release build's says **DodoSSH** —
which is the only difference visible while somebody is typing a passphrase into one of them. Signing in to
the nightly leaves the release build signed in and untouched, and the account shows a second device.
**Failure means:** if there is one profile directory, the two builds are sharing a cache and a device key,
and the next nightly carrying a schema migration will upgrade the database the release build opens. If
there is one install directory, the pack ids collide and the nightly has replaced the release build
outright — which is the thing ADR 0013 decision 9 is constructed to make impossible, so it means one of the
four separations has been undone.
**And the direction that matters most:** on the release build, PREFERENCES → UPDATES → CHECK NOW must not
offer a nightly, ever, however many have been published since. It reads a different index and refuses
prereleases; if a nightly version is ever offered there, stop and treat it as a release-channel incident
rather than as a bug in the nightly.
---
## Phase 17 — Installing and updating the phone