What changed, and why it matters
This commit only adds a line to the release notes document for LND 0.20.1, describing a previously merged bug fix. No actual code changes are included, so it cannot by itself introduce, fix, or exploit any security issue.
No action needed for this commit. If reviewing the related fix, examine PR #10383 directly.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to docs/release-notes/release-notes-0.20.1.md. It references pull request #10383, which fixed a startup deserialization issue in the mission control store by skipping and deleting bad entries. The commit itself does not modify any executable code, configuration, build, or test logic.
Changed components
docs/release-notes/release-notes-0.20.1.mdInspect captured patch +5 / −0
diff --git a/docs/release-notes/release-notes-0.20.1.md b/docs/release-notes/release-notes-0.20.1.md
index 4cc4556..844ae30 100644
--- a/docs/release-notes/release-notes-0.20.1.md
+++ b/docs/release-notes/release-notes-0.20.1.md
@@ -31,6 +31,11 @@
* Fix a bug where [repeated network
addresses](https://github.com/lightningnetwork/lnd/pull/10341) were added to
the node announcement and `getinfo` output.
+
+* [Fix a startup issue in LND when encountering a
+ deserialization issue](https://github.com/lightningnetwork/lnd/pull/10383)
+ in the mission control store. Now we skip over potential errors and also
+ delete them from the store.
# New Features
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.