Repository navigation
chore(contract): sync flipcash2 protos to 6de4f9ad (0.23.0) - #31
Merged
Merged
Conversation
This was referenced Oct 29, 2026
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.
Syncs the contract to
flipcash2-protobuf-api@6de4f9ad(upstream #160, #161, #162, #163) and adds the0.23.0changelog entry. Release as0.23.0.This upgrade breaks source in Swift only.
boosted_reactionon both activity crypto notification metadata messages moved into a newoneof context, sohasBoostedReactionis gone, andMetadataUpdate.kindgained a case that exhaustive switches must handle. Field numbers are unchanged, so the wire format is not affected.Contract changes
EditChatRequest.rules(field 6) edits a public group's listener and speaker minimum balances.MetadataUpdate.RulesChanged(oneof field 8) announces the edit.ChatUpdate.payment_request_updates(field 10), aPaymentRequestUpdateBatchofPaymentRequestUpdate:created, orUpdatesat a version made ofSharePaymentUpdateandStatusUpdate.activity.v1.RequestedPaymentasrequested_payment(oneof field 4) onDirectlySentCryptoNotificationMetadataandReceivedCryptoNotificationMetadata.push.v1.Push.SendTestPush.EditChatResponse.ResultINVALID_RULES = 7andRULES_NOT_SATISFIED = 8. Nothing was renumbered.App PRs
Both are drafts. They contain only the scaffolding and stay blocked until
0.23.0is published and their pins move. Neither applies payment request updates to UI state yet, and iOS does not persistrequestedPayment.