Skip to content

chore(contract): sync flipcash2 protos to 6de4f9ad (0.23.0) - #31

Merged
bmc08gt merged 2 commits into
mainfrom
chore/sync-flipcash2-6de4f9adfd11
Oct 29, 2026
Merged

bmc08gt merged 2 commits into
mainfrom
chore/sync-flipcash2-6de4f9adfd11

Conversation

@bmc08gt

@bmc08gt bmc08gt commented Oct 29, 2026

Copy link
Copy Markdown
Collaborator

Syncs the contract to flipcash2-protobuf-api@6de4f9ad (upstream #160, #161, #162, #163) and adds the 0.23.0 changelog entry. Release as 0.23.0.

This upgrade breaks source in Swift only. boosted_reaction on both activity crypto notification metadata messages moved into a new oneof context, so hasBoostedReaction is gone, and MetadataUpdate.kind gained a case that exhaustive switches must handle. Field numbers are unchanged, so the wire format is not affected.

Contract changes

  • Editable rules: EditChatRequest.rules (field 6) edits a public group's listener and speaker minimum balances. MetadataUpdate.RulesChanged (oneof field 8) announces the edit.
  • Payment request updates: ChatUpdate.payment_request_updates (field 10), a PaymentRequestUpdateBatch of PaymentRequestUpdate: created, or Updates at a version made of SharePaymentUpdate and StatusUpdate.
  • Feed links: activity.v1.RequestedPayment as requested_payment (oneof field 4) on DirectlySentCryptoNotificationMetadata and ReceivedCryptoNotificationMetadata.
  • Test push: push.v1.Push.SendTestPush.
  • Appended enum cases: EditChatResponse.Result INVALID_RULES = 7 and RULES_NOT_SATISFIED = 8. Nothing was renumbered.

App PRs

Both are drafts. They contain only the scaffolding and stay blocked until 0.23.0 is published and their pins move. Neither applies payment request updates to UI state yet, and iOS does not persist requestedPayment.

@bmc08gt bmc08gt self-assigned this Oct 29, 2026
@bmc08gt
bmc08gt merged commit 0bb7eef into main Oct 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant