Repository navigation
Release Android 0.6.121 with own-profile and message recovery fixes - #349
Merged
Merged
Conversation
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 even though their signed kind-0 profile had a name. Their own metadata was gated by the directory preference, was not carried into room/self tiles, and late profile updates did not reach the borrowed chat view.
Release Android 0.6.121 (code 144) with the own-profile fixes from #348 and the message replay recovery from #347. Own metadata follows the selected account and Nostr networking lifetime; other people’s directory preference remains separate. Private invitations stops public reads. Missing profiles get bounded retries. The current isolated recording playback implementation is retained.
This candidate combines the two reviewed source branches without modifying either source worktree or their prepared 0.6.120 artefacts. It supersedes the separate profile source PR for release qualification. All 17 executed CI checks, the exact-source production build, signing/lineage checks, signed upgrade, and publication readbacks remain required. Local profile tests and application compilation passed before integration; combined candidate qualification is pending. Physical GrapheneOS and actual owner/friend acceptance remain pending.