What changed, and why it matters
This commit only adds a line to the release notes document describing a bug fix from another pull request. It does not change any program code, so by itself it cannot introduce or fix a security issue. The actual bug fix happened elsewhere.
No action needed for this commit. Review PR #10330 directly if assessing the actual goroutine resource-leak fix.
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.20.0.md. It references PR #10330, which fixed a goroutine resource leak on disconnection or failure. No source code is modified in this commit.
Changed components
docs/release-notes/release-notes-0.20.0.mdInspect captured patch +3 / −0
diff --git a/docs/release-notes/release-notes-0.20.0.md b/docs/release-notes/release-notes-0.20.0.md
index f9d654d..e01f6cf 100644
--- a/docs/release-notes/release-notes-0.20.0.md
+++ b/docs/release-notes/release-notes-0.20.0.md
@@ -56,6 +56,9 @@
utxonursery (the legacy sweeper) where htlcs with a locktime of 0 would not
be swept.
+- [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.
+
# New Features
* Use persisted [nodeannouncement](https://github.com/lightningnetwork/lnd/pull/8825)
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.