What the developer wrote
Authored by ziggie
docs: add release-notes
What changed, and why it matters
This commit only adds a release note describing a previously fixed bug. It does not change any code, cryptographic logic, network behavior, or configuration. There is no security issue introduced or addressed by this documentation-only change.
No action required. This is a documentation-only release-note update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit is a documentation edit to docs/release-notes/release-notes-0.19.3.md. It appends a bullet point referencing PR #10125, which fixed a payment-lifecycle routing retry loop triggered by channel policy HTLC min/max violations. The diff contains no functional changes; it only records an already-merged fix and adds a contributor name.
Changed components
docs/release-notes/release-notes-0.19.3.mdInspect captured patch +6 / −0
diff --git a/docs/release-notes/release-notes-0.19.3.md b/docs/release-notes/release-notes-0.19.3.md
index 60f7c6b..241b905 100644
--- a/docs/release-notes/release-notes-0.19.3.md
+++ b/docs/release-notes/release-notes-0.19.3.md
@@ -29,6 +29,11 @@
imported in a watch-only (e.g. remote-signing)
setup](https://github.com/lightningnetwork/lnd/pull/10119).
+- [Fixed](https://github.com/lightningnetwork/lnd/pull/10125) a case in the
+ payment lifecycle where we would retry the same route over and over again in
+ situations where the sending amount would violate the channel policy
+ restriction (min,max HTLC).
+
# New Features
## Functional Enhancements
@@ -77,3 +82,4 @@
* Olaoluwa Osuntokun
* Oliver Gugger
* Yong Yu
+* Ziggie
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.