docs: update release notes for gossip v2 graph preparation
What changed, and why it matters
This commit only updates the release notes document. It adds a hyperlink to an already-merged pull request about preparing the graph database for a new gossip protocol version. No program code was changed, so it cannot by itself introduce or fix a security issue.
No security action needed. Treat as routine documentation update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a single Markdown edit in docs/release-notes/release-notes-0.21.0.md. It appends a third PR reference (10380) to an existing release-note bullet about ‘gossip V2’ graph DB preparation. There are no source-code, build, configuration, or documentation changes that alter behavior.
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 fc2a3fd..1c74a24 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -176,9 +176,10 @@
* 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
+* 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).
+ [2](https://github.com/lightningnetwork/lnd/pull/10379)
+ [3](https://github.com/lightningnetwork/lnd/pull/10380).
## 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.