What changed, and why it matters
This commit only updates the release notes document. It adds text describing two earlier changes: a switch in how LND checks Bitcoin peer health, and clearer wording for a warning about ZMQ port mismatches. There is no code change in this commit itself.
No action needed for this documentation-only commit. Review the referenced PR #10686 and issue #10568 separately if assessing the underlying changes.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies docs/release-notes/release-notes-0.22.0.md. It documents that bitcoind outbound peer health checks now use getnetworkinfo.connections_out rather than getpeerinfo, and that ZMQ port-mismatch warning messages were clarified. No functional code is changed.
Changed components
docs/release-notes/release-notes-0.22.0.mdInspect captured patch +6 / −0
diff --git a/docs/release-notes/release-notes-0.22.0.md b/docs/release-notes/release-notes-0.22.0.md
index dc9b3c6..fb31bad 100644
--- a/docs/release-notes/release-notes-0.22.0.md
+++ b/docs/release-notes/release-notes-0.22.0.md
@@ -21,6 +21,11 @@
# Bug Fixes
+* Bitcoind outbound peer health checks [now use](https://github.com/lightningnetwork/lnd/pull/10686)
+ `getnetworkinfo.connections_out` instead of `getpeerinfo`. The same PR also
+ [clarifies](https://github.com/lightningnetwork/lnd/issues/10568) the ZMQ
+ port-mismatch warnings so they no longer suggest that the connection failed.
+
# New Features
## Functional Enhancements
@@ -64,4 +69,5 @@
# Contributors (Alphabetical Order)
+* Boris Nagaev
* Erick Cestari
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.