docs: add release notes for KV-to-SQL payment migration
What changed, and why it matters
This commit only adds a line to the release notes describing an internal database migration for payment records (moving from a key-value format to SQL). It does not change any code, configuration, or security behavior. There is no security issue in this commit itself.
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 patch is a documentation-only addition to docs/release-notes/release-notes-0.21.0.md. It references pull request #10485, which adds a KV-to-SQL payment database migration. The note clarifies the migration is currently dev-only and gated behind test build tags. No executable code, tests, or configuration are modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +4 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 0679bb9..5c456d2 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -217,6 +217,10 @@
db functions Part 2](https://github.com/lightningnetwork/lnd/pull/10308)
* [Finalize SQL implementation for
payments db](https://github.com/lightningnetwork/lnd/pull/10373)
+ * [Add the KV-to-SQL payment
+ migration](https://github.com/lightningnetwork/lnd/pull/10485) with
+ comprehensive tests. The migration is currently dev-only, compiled behind
+ the `test_db_postgres`, `test_db_sqlite`, or `test_native_sql` build tags.
## 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.