What changed, and why it matters
This commit only adds a single line to the release notes document, linking to a prior code change about finalizing a SQL database implementation for payment records. There is no actual code change, no bug fix, and no security content in the diff itself.
No security action needed. Review the linked PR #10373 separately if assessing the SQL payments migration for correctness or performance, but that work is outside this commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only edit to docs/release-notes/release-notes-0.21.0.md, appending a bullet point that references GitHub pull request #10373 (‘Finalize SQL implementation for payments db’). No source code, configuration, or cryptographic logic is modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +2 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 0683f38..0679bb9 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -215,6 +215,8 @@
db functions Part 1](https://github.com/lightningnetwork/lnd/pull/10307)
* [Thread context through payment
db functions Part 2](https://github.com/lightningnetwork/lnd/pull/10308)
+ * [Finalize SQL implementation for
+ payments db](https://github.com/lightningnetwork/lnd/pull/10373)
## 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.