docs: add release note for EstimateRouteFee outgoing chans
What changed, and why it matters
This commit only adds documentation to the release notes describing a new feature: the ability to restrict fee estimates to specific first-hop outgoing channels in the EstimateRouteFee RPC and lncli command. There is no code change, no bug fix, and no security-related content.
No security action needed; this is a documentation-only release note update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds two bullet points to docs/release-notes/release-notes-0.22.0.md documenting PR #10501, which introduced outgoing_chan_ids support in routerrpc.EstimateRouteFee and –outgoing_chan_id in the estimateroutefee lncli command. The change is purely informational release-note text.
Changed components
docs/release-notes/release-notes-0.22.0.mdInspect captured patch +10 / −0
diff --git a/docs/release-notes/release-notes-0.22.0.md b/docs/release-notes/release-notes-0.22.0.md
index c3367af..5ca0180 100644
--- a/docs/release-notes/release-notes-0.22.0.md
+++ b/docs/release-notes/release-notes-0.22.0.md
@@ -27,8 +27,18 @@
## RPC Additions
+* The `routerrpc.EstimateRouteFee` RPC now supports [restricting fee estimates
+ to specific first-hop outgoing
+ channels](https://github.com/lightningnetwork/lnd/pull/10501) via the new
+ `outgoing_chan_ids` field in `RouteFeeRequest`.
+
## lncli Additions
+* The `estimateroutefee` command now supports [restricting fee estimates to
+ specific first-hop outgoing
+ channels](https://github.com/lightningnetwork/lnd/pull/10501) via the new
+ `--outgoing_chan_id` flag.
+
# Improvements
## Functional Updates
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.