What changed, and why it matters
This commit only adds a line to the release notes document describing a bug fix that was already merged in a separate pull request. No code was changed, so this commit itself does not fix or introduce any security issue.
No action needed for this documentation commit. Review PR #10371 separately if you want to assess the actual bug fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only change to docs/release-notes/release-notes-0.20.1.md. It adds a bullet point referencing PR #10371, which fixed a source-node race condition that could prevent startup. The actual fix is not present in this commit; only the release-note entry is added.
Changed components
docs/release-notes/release-notes-0.20.1.mdInspect captured patch +5 / −0
diff --git a/docs/release-notes/release-notes-0.20.1.md b/docs/release-notes/release-notes-0.20.1.md
index 844ae30..f1e7023 100644
--- a/docs/release-notes/release-notes-0.20.1.md
+++ b/docs/release-notes/release-notes-0.20.1.md
@@ -31,6 +31,11 @@
* Fix a bug where [repeated network
addresses](https://github.com/lightningnetwork/lnd/pull/10341) were added to
the node announcement and `getinfo` output.
+
+* [Fix source node race
+ condition](https://github.com/lightningnetwork/lnd/pull/10371) which could
+ prevent a node from starting up if two goroutines attempt to update the
+ node's announcement at the same time.
* [Fix a startup issue in LND when encountering a
deserialization issue](https://github.com/lightningnetwork/lnd/pull/10383)
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.