docs: release notes entries removed for prs merged with release v0.20.1
What the developer wrote
Authored by saubyk
docs: release notes entries removed for prs merged with release v0.20.1
What changed, and why it matters
This commit only removes two entries from the draft release notes for version 0.21.0. The entries describe bug fixes that were already merged into the earlier 0.20.1 release, so they are being deleted from the wrong document. No code was changed, and no new security issue is introduced or fixed by this commit.
No security action needed. If reviewing the underlying PRs #10399 and #10420, evaluate them separately in their own commits.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff deletes 13 lines from docs/release-notes/release-notes-0.21.0.md. The removed lines reference PRs #10399 (TLS manager file regeneration) and #10420 (channel graph race conditions), which were merged with v0.20.1 and therefore should not appear in the v0.21.0 release notes. This is a documentation cleanup only; the actual code changes live in other commits.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +0 / −13
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index e7cf03f..c9d458d 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -32,19 +32,6 @@
sub-server is still starting. This allows clients to reliably detect the
transient condition and retry without brittle string matching.
-- [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/10420) 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`.
-
- [Fixed TLV decoders to reject malformed records with incorrect lengths](https://github.com/lightningnetwork/lnd/pull/10249).
TLV decoders now strictly enforce fixed-length requirements for Fee (8 bytes),
Musig2Nonce (66 bytes), ShortChannelID (8 bytes), Vertex (33 bytes), and
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.