docs: add missing v0.20.1 release notes from release branch
What the developer wrote
Authored by saubyk
docs: add missing v0.20.1 release notes from release branch
What changed, and why it matters
This commit only adds text to the release notes document for version 0.20.1. It describes several previously merged bug fixes (TLS file handling, database race conditions, SQL connection limits, feature-bit parsing, and a gossiper deadlock), but it does not change any source code, configuration, or executable behavior. By itself, it cannot introduce or fix a security issue.
No security action is required for this documentation commit. Review the separately merged pull requests (10399, 10433, 10428, 10435, 10540) if you wish to assess the actual fixes.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only update to docs/release-notes/release-notes-0.20.1.md. It adds prose descriptions and pull-request links for five already-merged fixes and one contributor name. No code, build scripts, tests, or dependencies are modified. The underlying fixes referenced in the notes were merged separately and are not part of this commit.
Changed components
docs/release-notes/release-notes-0.20.1.mdInspect captured patch +20 / −0
diff --git a/docs/release-notes/release-notes-0.20.1.md b/docs/release-notes/release-notes-0.20.1.md
index 81b9ed3..1c5cb7e 100644
--- a/docs/release-notes/release-notes-0.20.1.md
+++ b/docs/release-notes/release-notes-0.20.1.md
@@ -48,6 +48,19 @@
in the mission control store. Now we skip over potential errors and also
delete them from the store.
+* [Fixed an issue](https://github.com/lightningnetwork/lnd/pull/10399) where the
+ TLS manager would fail to start if only one of the TLS pair files (certificate
+ or key) existed. The manager now correctly regenerates both files when either
+ is missing, preventing "file not found" errors on startup.
+
+* [Fixed race conditions](https://github.com/lightningnetwork/lnd/pull/10433) in
+ the channel graph database. The `Node.PubKey()` and
+ `ChannelEdgeInfo.NodeKey1/NodeKey2()` methods had check-then-act races when
+ caching parsed public keys. Additionally, `DisconnectBlockAtHeight` was
+ accessing the reject and channel caches without proper locking. The caching
+ has been removed from the public key parsing methods, and proper mutex
+ protection has been added to the cache access in `DisconnectBlockAtHeight`.
+
* [Fix potential sql tx exhaustion
issue](https://github.com/lightningnetwork/lnd/pull/10428) in LND which might
happen when running postgres with a limited number of connections configured.
@@ -69,6 +82,12 @@
The fix adds automatic format detection to handle both legacy (raw feature
bits) and new (length-prefixed) formats.
+* [Fixed a shutdown
+ deadlock](https://github.com/lightningnetwork/lnd/pull/10540) in the gossiper.
+ Certain gossip messages could cause multiple error messages to be sent on a
+ channel that was only expected to be used for a single message. The erring
+ goroutine would block on the second send, leading to a deadlock at shutdown.
+
# New Features
## Functional Enhancements
@@ -139,5 +158,6 @@
* Abdulkbk
* bitromortac
+* Matt Morehouse
* Olaoluwa Osuntokun
* Ziggie
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.