Repository navigation
Release desktop 0.1.109 and Android 0.6.121 with own-profile recovery - #595
Merged
TheCryptoDonkey merged 14 commits intoOct 27, 2026
Merged
Conversation
TheCryptoDonkey
deleted the
release/profile-names-desktop109-android121-20261027
branch
October 27, 2026 11:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Signed-in accounts could appear as Somebody because own-account kind-0 metadata shared the optional directory lookup switch. Android additionally failed to carry late account profiles into room and borrowed-chat state. The desktop phone-width identity panel also hid a loaded name.
Release desktop preview 0.1.109 and publish the production-signed Android 0.6.121 (code 144) download metadata. Desktop’s own-account profile is loaded independently of optional lookups for other people; private invitations still stops public reads, account changes discard old work, missing profiles retry within a bounded lifetime, and explicit Nostr-address verification is preserved. The own name remains visible in How you appear at phone widths. Android source/signing qualification is tracked in forgesworn/kithmoot-android#349.
This candidate includes the source fixes from #594 and the delivery/security updates prepared in #593, preserving the earlier candidates and their evidence. The six new desktop packages retain Electron 44.9.3 and the credential-expiry draft guard. Android includes the replay recovery from forgesworn/kithmoot-android#347. No existing immutable download is replaced.
Validation: 7,985 web/library tests passed (three existing skips); 255 desktop tests passed (two existing skips); 10 update-feed/manifest and 13 Android-publication-verifier tests passed. All four desktop platform ASARs are identical and match 591 web files plus 27 native JS/CJS files. All six archive/DEB payloads match their packaged trees; Debian root ownership and sandbox mode verified. Mac Developer ID signing, notarisation, staple, Gatekeeper and isolated packaged-app smoke passed. The desktop tooling audit is clean. Both update manifests have valid signatures from the existing release key. Android’s exact signed APK passed independent signature/lineage/publication verification and an API 35 emulator upgrade with encrypted synthetic data retained; all 17 storage/native/playback checks passed and the task emulator was removed.
Desktop runtime was built from 7a1e6dc; only publication metadata/evidence changed afterwards. A full runtime file manifest records this boundary. Final hosted CI and production publication/readback remain pending. Physical GrapheneOS/Linux/Mac and actual owner/friend acceptance remain pending. These are standalone KithMoot screens; no Archipelago integration is changed.