What the developer wrote
Authored by Boris Nagaev
docs: add release notes entry
Also fixed a typo in release notes.
What changed, and why it matters
This commit only updates the release notes document. It adds a description of an earlier code change (a gRPC status code improvement for chain notifier RPCs) and fixes a spelling typo. There are no code changes in this commit itself, so it cannot introduce or fix any security vulnerability directly.
No security action needed. This is a documentation-only commit. If reviewing the referenced PR #10352 for security relevance, evaluate it separately.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is limited to docs/release-notes/release-notes-0.20.0.md. It inserts a bullet describing PR #10352, which makes chain notifier RPCs return gRPC status UNAVAILABLE while the sub-server is starting, and corrects ‘recgonize’ to ‘recognize’. No source code is modified.
Changed components
docs/release-notes/release-notes-0.20.0.mdInspect captured patch +6 / −1
diff --git a/docs/release-notes/release-notes-0.20.0.md b/docs/release-notes/release-notes-0.20.0.md
index e01f6cf..03b2c27 100644
--- a/docs/release-notes/release-notes-0.20.0.md
+++ b/docs/release-notes/release-notes-0.20.0.md
@@ -59,6 +59,11 @@
- [Fixed a bug](https://github.com/lightningnetwork/lnd/pull/10330) to ensure that goroutine resources are properly freed in the case
of a disconnection or other failure event.
+- Chain notifier RPCs now [return the gRPC `Unavailable`
+ status](https://github.com/lightningnetwork/lnd/pull/10352) while the
+ sub-server is still starting. This allows clients to reliably detect the
+ transient condition and retry without brittle string matching.
+
# New Features
* Use persisted [nodeannouncement](https://github.com/lightningnetwork/lnd/pull/8825)
@@ -283,7 +288,7 @@ reader of a payment request.
* [Require invoices to include a payment address or blinded paths](https://github.com/lightningnetwork/lnd/pull/9752)
to comply with updated BOLT 11 specifications before sending payments.
-* [LND can now recgonize DNS address type in node
+* [LND can now recognize DNS address type in node
announcement msg](https://github.com/lightningnetwork/lnd/pull/9455). This
allows users to forward node announcement with valid DNS address types. The
validity aligns with Bolt 07 DNS constraints.
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.