From 1306376984342b7fbbc8f4048e1c7745443f514b Mon Sep 17 00:00:00 2001
From: saubyk <39208279+saubyk@users.noreply.github.com>
Date: Tue, 17 Mar 2026 15:29:08 -0700
Subject: [PATCH] docs: release notes entries removed for prs merged with
 release v0.20.1

---
 docs/release-notes/release-notes-0.21.0.md | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index e7cf03f52..c9d458d18 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