Repository navigation
v1.0.2
Reliability fixes, mostly in places that were failing silently.
Sharing invitations could never find some accounts
If your email had a capital letter when you signed up (Foo@example.com), your profile was stored exactly like that while colleagues were searched for in lower case — so you could never be found, and the person inviting you just saw "no such account". Both sides are now normalized. Existing profiles are corrected when the database schema is reapplied.
Change history could break permanently
Two devices saving at once could record the same version number twice, and rolling back to that version then failed forever. Version numbers are now unique, and a collision retries instead of leaving a broken pair. Existing duplicates are renumbered — moved to free numbers rather than deleted, so no history is lost.
Switching authentication left the old secret behind
Changing a server from password to SSH key without pasting a key kept the unused password in the credential store, while the connection was attempted with an empty key. The old secret is now removed when the method changes.
Also
- A stored authentication value out of range no longer takes down the whole server list.
- With no host-key verifier the connection is now refused rather than accepting any key. Every path in the app supplies one; the safe default matters if a future one forgets.
- The local database now declares a migration strategy — without it, the first schema change would have stopped existing installs from opening their data at all.
- In-app inquiries: the contact form no longer reports success when the server could not store the message, and the server function works under both Supabase API key schemes.
Windows: trust the certificate once before installing, in an admin PowerShell:
Import-Certificate -FilePath .\kerminal-codesign.cer -CertStoreLocation Cert:\LocalMachine\RootAndroid, upgrading from 0.5.x or earlier: the signing key changed in 0.6.0, so the app installs alongside the old one. Use Settings → Backup → Save to file… in the old version, then restore it here. Upgrades from 0.6.0 onwards are normal.
Full details: CHANGELOG.md