Skip to content

docs(changelog): name 0.5.0's new field on TipDmPayment, not PaymentMetadata #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bmc08gt merged 1 commit into from
Sep 11, 2026
Merged

docs(changelog): name 0.5.0's new field on TipDmPayment, not PaymentMetadata #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ picking up three upstream changes: [#90](https://github.com/code-payments/flipca
makes a pushed message, a `SendMessage` echo, and an event-stream delivery of the same message
interchangeable, which is what lets a push be written straight into local storage.

- `action` on `intent.v1.ChatMetadata.PaymentMetadata`, field 2, with a new nested `Action` enum —
- `action` on `intent.v1.ChatMetadata.TipDmPayment`, field 2, with a new nested `Action` enum —
`DEFAULT = 0`, `SEND = 1`, `TIP = 2`. `DEFAULT` means infer from `location`, so a sender that
leaves it unset keeps the behaviour it has today.

Expand Down Expand Up @@ -62,7 +62,7 @@ picking up three upstream changes: [#90](https://github.com/code-payments/flipca
### Unchanged

Nothing was renumbered, and no result enum gained or reordered a case. `push.v1.ChatMetadata` keeps
fields 1 and 2 and appends 3; `PaymentMetadata` keeps `location` on 1 and appends 2; and
fields 1 and 2 and appends 3; `TipDmPayment` keeps `location` on 1 and appends 2; and
`user_events` keeps field number 1 inside its new oneof, so `ForwardEventsRequest` is wire-compatible
and only its generated API moved. No service, RPC or message was removed.

Expand Down
Loading