What changed, and why it matters
This commit only updates the release notes documentation. It adds a single bullet describing a prior code change that limits two peer-tracking metrics to peers that share channels. There is no code change, no bug fix, and no security-relevant content in the commit itself.
No action required. This is a documentation-only release-notes update with no security implications.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one bullet to docs/release-notes/release-notes-0.20.0.md noting that FlapCount and LastFlapNs now track only peers with channels. This is a documentation-only update referencing an already-merged pull request (#10211). No functional code is modified.
Changed components
docs/release-notes/release-notes-0.20.0.mdInspect captured patch +4 / −0
diff --git a/docs/release-notes/release-notes-0.20.0.md b/docs/release-notes/release-notes-0.20.0.md
index 50653dc..e77089e 100644
--- a/docs/release-notes/release-notes-0.20.0.md
+++ b/docs/release-notes/release-notes-0.20.0.md
@@ -186,6 +186,10 @@ circuit. The indices are only available for forwarding events saved after v0.20.
for the case where the DB is kvdb backed and no invoices have yet been added
to the database.
+* The `FlapCount` and `LastFlapNs` have been
+ [changed](https://github.com/lightningnetwork/lnd/pull/10211) to track
+ exclusively for peers that have channels with us.
+
## lncli Updates
* Previously, users could only specify one `outgoing_chan_id` when calling the
`lncli queryroutes` or the QueryRoutes RPC. With this change, multiple
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.