chore(contract): sync flipcash2 protos to 89b444bc and add the 0.7.0 entry - #13
Merged
Merged
Conversation
Group chat RPCs, roster updates on the event stream, and the removal of event.v1.ChatUpdate.new_messages. publish.yml reads the section matching the version it publishes, so 0.7.0 cannot release without this.
This was referenced Sep 15, 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
1 participant
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@89b444bc,picking up upstream #99 and #100, and adds the
0.7.0changelog entry thatpublish.ymlneeds inorder to release that version.
One field goes away:
event.v1.ChatUpdate.new_messages, field 2, nowreserved 2. It has carried[deprecated = true]since 0.1.0 andeventshas sat beside it as the sequenced replacement forjust as long, so this breaks only a consumer still reading the deprecated field. Neither app is:
Android dropped its last
newMessagesreference in #1441, and iOS never had one.Everything else is additive.
Group chat RPCs —
GetGroupChatFeed,StartChat,JoinChatandLeaveChatonservice Chat,which is what makes
chat/v1/chat_service.protoimportblob/v1/model.protoandmoderation/v1/model.protofor the first time.GetGroupChatFeedhas the samepagination-plus-stream read contract as
GetDmChatFeed, with one wrinkle the DM feed does not have:membership can change mid-read, so a group left between pages is absent from the paginated set and
its removal arrives on the stream instead.
Roster updates —
chat.v1.RosterUpdate/RosterUpdateBatch, delivered onevent.v1.ChatUpdate.roster_updates(field 8). These are a convergent overlay riding the streamoutside the gap-detected event log, applied by
RosterSummary.version— greater applies, lesser orequal drops, so delivery order does not matter. A miss is reconciled by refetching the roster rather
than through
GetDelta.common.v1.PagingToken.valueraises its validationmax_lenfrom 128 to 16384, because thegroup feed packs the snapshot's remaining order into the token. Validation ceiling only — same field,
same number, no generated API change.
Nothing was renumbered. All four new
Resultenums are on brand-new messages, so the positionalError*(rawValue:)mapping on iOS is untouched.Consumers
Both apps are scaffolded and building against this checkout through the local override, each on a
branch that pins
0.7.0. Both are drafts until this merges and0.7.0publishes, since neither canresolve the pin before then.