What the developer wrote
Authored by yyforyongyu
docs: update release note
What changed, and why it matters
This commit only updates the release notes document. It adds a description of a previously fixed bug where LND would disconnect peers over a specific type of ping message. There are no code changes in this commit, so it does not introduce, fix, or change any behavior by itself.
No action needed for this commit. If reviewing the underlying PR #10674, evaluate the actual code change there separately.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to docs/release-notes/release-notes-0.21.0.md. It describes PR #10674, which fixed handling of BOLT 1 pings requesting 65532 or more pong bytes. The actual fix is not present in this commit; only the release-note entry is added.
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 a57ca9e..cb5fa1a 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -56,6 +56,12 @@
transitions during startup, avoiding lost unlocks during slow database
initialization.
+* [Fixed handling of BOLT 1 pings requesting 65532 or more pong
+ bytes](https://github.com/lightningnetwork/lnd/pull/10674). LND now ignores
+ these valid no-reply pings instead of disconnecting peers, restoring
+ compatibility with implementations that pad `channel_reestablish` messages
+ with them.
+
# New Features
- [Basic Support](https://github.com/lightningnetwork/lnd/pull/9868) for onion
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.