docs: add release note for versioned graph horizon queries
What changed, and why it matters
This commit only adds a release note describing an earlier code change. It does not change any program code, database logic, or network behavior. There is no security issue in this documentation edit.
No action needed; this is a documentation-only release-note entry.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit appends a single bullet to docs/release-notes/release-notes-0.21.0.md summarizing PR #10691, which versioned graph horizon queries and adjusted the v1 end-time bound from inclusive to exclusive to match BOLT 07. The diff is purely documentation (+6 lines, no code changes).
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +6 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 0086c11..6d01937 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -292,6 +292,12 @@
[4](https://github.com/lightningnetwork/lnd/pull/10542),
[5](https://github.com/lightningnetwork/lnd/pull/10572),
[6](https://github.com/lightningnetwork/lnd/pull/10582).
+* [Version the graph horizon queries (`NodeUpdatesInHorizon`,
+ `ChanUpdatesInHorizon`)](https://github.com/lightningnetwork/lnd/pull/10691)
+ to support both v1 (time-based) and v2 (block-height-based) gossip ranges.
+ The v1 end-time bound is corrected from inclusive to exclusive to match the
+ BOLT 07 `gossip_timestamp_filter` spec. New SQL queries and composite indexes
+ are added for efficient v2 block-height range scans.
* Updated waiting proof persistence for gossip upgrades by introducing typed
waiting proof keys and payloads, with a DB migration to rewrite legacy
waiting proof records to the new key/value format
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.