docs: sync the v0.21.5 release notes with the release branch
What changed, and why it matters
This commit only reorders two existing entries in the release notes document for version 0.21.5. No code, configuration, or behavior of the LND software is changed. It is a documentation-only edit to keep two copies of the release notes in the same order.
No action needed; this is a non-functional documentation change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff shows a pure reordering of two bullet points in docs/release-notes/release-notes-0.21.5.md. One bullet about MuSig2 session cleanup and another about auxiliary HTLC signature validation swap positions. The text content, links, and meaning are unchanged. There are no source-code modifications.
Changed components
docs/release-notes/release-notes-0.21.5.mdInspect captured patch +9 / −9
### docs/release-notes/release-notes-0.21.5.md
@@ -26,15 +26,6 @@
The remote party's next revocation point now uses `fn.Option`, so callers
handle the optional state explicitly.
-* Taproot commitment signing and verification now [release transient MuSig2
- signer sessions](https://github.com/lightningnetwork/lnd/pull/11246) once
- the local node no longer needs them. Force-close and cooperative-close
- signing continue to retain their sessions until signature combination, with
- cooperative-close rounds releasing their session when the round completes
- or is aborted. Invalid MuSig2 partial commitment signatures are now rejected
- with the commitment height and transaction attached, and those debug details
- are sent to the remote peer.
-
* [Tightened the validation](https://github.com/lightningnetwork/lnd/pull/11068)
of auxiliary HTLC signatures on taproot overlay channels. Their count is now
checked against the number of HTLCs on the commitment, mirroring the check
@@ -48,6 +39,15 @@
a commitment carries an HTLC. Peers running an older `tapd` with the aux
signer attached are unaffected.
+* Taproot commitment signing and verification now [release transient MuSig2
+ signer sessions](https://github.com/lightningnetwork/lnd/pull/11246) once
+ the local node no longer needs them. Force-close and cooperative-close
+ signing continue to retain their sessions until signature combination, with
+ cooperative-close rounds releasing their session when the round completes
+ or is aborted. Invalid MuSig2 partial commitment signatures are now rejected
+ with the commitment height and transaction attached, and those debug details
+ are sent to the remote peer.
+
* Native SQLite graph migrations [now accept policies with empty
signatures](https://github.com/lightningnetwork/lnd/pull/11311) instead of
failing validation because the KV and SQL stores use different empty byteWhy 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.