What the developer wrote
Authored by Oliver Gugger
docs: move v0.19.3 items to correct file
Moves the PRs that are going to be shipped with v0.19.3 into the correct
release notes file.
What changed, and why it matters
This commit is purely a documentation housekeeping change. It moves release note entries for three already-merged changes (a logging fix, a deadlock fix, and gossip bandwidth default increases) from the v0.20.0 file to the v0.19.3 file because they are actually shipping in the earlier v0.19.3 release. No code behavior is changed.
No security action needed; this is a release-notes reorganization. Review the referenced PRs (10096, 10107, 10108) separately if their security relevance needs assessment.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff only edits two markdown release notes files. It removes three bullet points from docs/release-notes/release-notes-0.20.0.md and adds equivalent bullet points to docs/release-notes/release-notes-0.19.3.md, plus adds one contributor name. The underlying PRs (10096, 10107, 10108) are referenced but their code is not modified here.
Changed components
docs/release-notes/release-notes-0.19.3.mddocs/release-notes/release-notes-0.20.0.mdInspect captured patch +13 / −12
diff --git a/docs/release-notes/release-notes-0.19.3.md b/docs/release-notes/release-notes-0.19.3.md
index 241b905..5179a89 100644
--- a/docs/release-notes/release-notes-0.19.3.md
+++ b/docs/release-notes/release-notes-0.19.3.md
@@ -25,6 +25,14 @@
messages simultaneously. The fix ensures only a single goroutine processes the
backlog at any given time using an atomic flag.
+- [Fix](https://github.com/lightningnetwork/lnd/pull/10107) a bug where child
+ logger's derived via `WithPrefix` did not inherit change log level changes
+ from their parent loggers.
+
+- Fixed a [deadlock](https://github.com/lightningnetwork/lnd/pull/10108) that
+ can cause contract resolvers to be stuck at marking the channel force close as
+ being complete.
+
- [Fixed a bug in `btcwallet` that caused issues with Tapscript addresses being
imported in a watch-only (e.g. remote-signing)
setup](https://github.com/lightningnetwork/lnd/pull/10119).
@@ -38,6 +46,10 @@
## Functional Enhancements
+* The default value for `gossip.msg-rate-bytes` has been
+ [increased](https://github.com/lightningnetwork/lnd/pull/10096) from 100KB to
+ 1MB, and `gossip.msg-burst-bytes` has been increased from 200KB to 2MB.
+
- Previously, when sweeping non-time sensitive anchor outputs, they might be
grouped with other non-time sensitive outputs such as `to_local` outputs,
which potentially allow the sweeping tx to be pinned. This is now
@@ -79,6 +91,7 @@
# Contributors (Alphabetical Order)
+* Elle Mouton
* Olaoluwa Osuntokun
* Oliver Gugger
* Yong Yu
diff --git a/docs/release-notes/release-notes-0.20.0.md b/docs/release-notes/release-notes-0.20.0.md
index a6bc8d2..0c3df27 100644
--- a/docs/release-notes/release-notes-0.20.0.md
+++ b/docs/release-notes/release-notes-0.20.0.md
@@ -37,13 +37,6 @@
known TLV fields were incorrectly encoded into the `ExtraData` field of
messages in the dynamic commitment set.
-- Fixed a [deadlock](https://github.com/lightningnetwork/lnd/pull/10108) that
- can cause contract resolvers to be stuck at marking the channel force close as
- being complete.
-
-- [Fix](https://github.com/lightningnetwork/lnd/pull/10107) a bug where child
- logger's derived via `WithPrefix` did not inherit change log level changes
- from their parent loggers.
# New Features
@@ -86,11 +79,6 @@ circuit. The indices are only available for forwarding events saved after v0.20.
finish under this timeout value. Consider using a larger timeout value if you
have a slow network.
-* The default value for `gossip.msg-rate-bytes` has been
- [increased](https://github.com/lightningnetwork/lnd/pull/10096) from 100KB to
- 1MB, and `gossip.msg-burst-bytes` has been increased from 200KB to 2MB.
-
-
* Added [`deletecanceledinvoices`](
https://github.com/lightningnetwork/lnd/pull/9625) RPC to allow the removal of
a canceled invoice. Supports deleting a canceled invoice by providing its
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.