What changed, and why it matters
This commit only updates the release notes documentation. It adds a second pull request link to an existing note about preparing the graph database for a future protocol feature (gossip v2). No code, logic, or configuration changes are present in the diff.
No security action required. This is a documentation-only release-notes update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a one-line documentation edit in docs/release-notes/release-notes-0.21.0.md. It rewords the existing ‘Prepare the graph DB for handling gossip V2 nodes’ bullet to also reference PR 10379 for channel handling. There are no source-code, build, or dependency changes.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +3 / −2
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 0040da7..fc2a3fd 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -176,8 +176,9 @@
* Freeze the [graph SQL migration
code](https://github.com/lightningnetwork/lnd/pull/10338) to prevent the
need for maintenance as the sqlc code evolves.
-* Prepare the graph DB for handling gossip [V2
- nodes](https://github.com/lightningnetwork/lnd/pull/10339).
+* Prepare the graph DB for handling gossip V2
+ nodes and channels [1](https://github.com/lightningnetwork/lnd/pull/10339)
+ [2](https://github.com/lightningnetwork/lnd/pull/10379).
## Code Health
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.