[v0.20.x-branch] Backport #11024: invoices: refine update handling - #11026
Merged
Conversation
ziggie1984
approved these changes
Aug 5, 2026
ziggie1984
left a comment
ziggie1984
left a comment
Collaborator
There was a problem hiding this comment.
LGTM (no merge conflicts)
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.
Backport of #11024
Summary
Motivation
Invoice updates can take different paths depending on invoice features and the payment payload. This change keeps path selection and outcomes aligned across those combinations.
Testing
go test ./invoices