What the developer wrote
Authored by yyforyongyu
docs: add EstimateRouteFee release note
What changed, and why it matters
This commit only adds a release note describing a bug fix that was already merged elsewhere. The actual code change happened in a previous pull request. There is no new executable code in this commit, so it does not introduce or fix a vulnerability by itself.
No action needed for this documentation commit. Review PR #10771 separately if assessing the underlying fix.
Security signals we found
Release note references a prior bug fix in routing/fee estimation logic
Evidence from the diff
The diff adds four lines to docs/release-notes/release-notes-0.21.0.md documenting that PR #10771 fixed EstimateRouteFee to use independent probe payment hashes when probing multiple LSPs, preventing later probes from reusing the first probe’s CLTV delta. No source code is modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +4 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 23b93a0..f7b9939 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -88,6 +88,10 @@
RBF close state machine does not yet thread through the `AuxCloser` hook
that overlay channels rely on to build aux-aware close transactions.
+* [Fixed `EstimateRouteFee`](https://github.com/lightningnetwork/lnd/pull/10771)
+ to use independent probe payment hashes when probing multiple LSPs, preventing
+ later probes from reusing the first probe's CLTV delta.
+
# New Features
- [Basic Support](https://github.com/lightningnetwork/lnd/pull/9868) for onion
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.