What changed, and why it matters
This commit only updates the release notes document. It adds a description of a previously fixed startup bug related to TLS certificate/key files and adds a contributor name. There is no code change in this commit itself.
No action needed for this documentation-only commit. Review PR #10399 separately if assessing the underlying TLS manager fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies docs/release-notes/release-notes-0.21.0.md, adding a bullet describing PR #10399 which fixed TLS manager startup behavior when only one of the certificate/key pair files exists. It also adds ‘Mohamed Awnallah’ to the contributor list. No functional code is changed.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +6 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index 04b4290..d15df41 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -26,6 +26,11 @@
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.
+
# New Features
- Basic Support for [onion messaging forwarding](https://github.com/lightningnetwork/lnd/pull/9868)
@@ -77,4 +82,5 @@
* Boris Nagaev
* Elle Mouton
+* Mohamed Awnallah
* Nishant Bansal
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.