What changed, and why it matters
This commit only updates the release notes document. It adds a one-line description of a previously merged bug fix (PR #10410) about graph database edges for a node's own channels. There are no code changes in this commit, so it cannot by itself introduce, fix, or enable any security issue.
No security action needed for this documentation commit. Review PR #10410 separately if you want to assess the actual bug fix's security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to docs/release-notes/release-notes-0.20.1.md. It records that PR #10410 fixed a bug where missing edges for own channels could not be added to the graph DB after graph-refactor validation checks resurfaced. No source code, build scripts, tests, or configuration files are modified.
Changed components
docs/release-notes/release-notes-0.20.1.mdInspect captured patch +5 / −0
diff --git a/docs/release-notes/release-notes-0.20.1.md b/docs/release-notes/release-notes-0.20.1.md
index 8e0e9bc..3448940 100644
--- a/docs/release-notes/release-notes-0.20.1.md
+++ b/docs/release-notes/release-notes-0.20.1.md
@@ -50,6 +50,11 @@
invoice](https://github.com/lightningnetwork/lnd/pull/10439). This makes sure
the EstimateRouteFee API can probe Eclair and LDK nodes which enforce the
payment address/secret.
+
+* Fix a bug where [missing edges for own channels could not be added to the
+ graph DB](https://github.com/lightningnetwork/lnd/pull/10410)
+ due to validation checks in the graph Builder that were resurfaced after the
+ graph refactor work.
# New Features
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.