What changed, and why it matters
This commit only updates the release notes document. It adds a one-line description of an earlier code change about detecting Taproot activation, and adds a contributor's name to the credits list. There are no code changes and no security fix or vulnerability described.
No security action needed. This is a documentation-only commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is limited to docs/release-notes/release-notes-0.21.0.md. It adds a bullet under ‘Code Health’ referencing PR #10683 (‘Update taproot detection to accommodate buried activation…’) and adds ‘Matthew Zipkin’ to the contributor list. No source code, build scripts, tests, or configuration files are modified.
Changed components
docs/release-notes/release-notes-0.21.0.mdInspect captured patch +5 / −0
diff --git a/docs/release-notes/release-notes-0.21.0.md b/docs/release-notes/release-notes-0.21.0.md
index ad58f77..10bf65e 100644
--- a/docs/release-notes/release-notes-0.21.0.md
+++ b/docs/release-notes/release-notes-0.21.0.md
@@ -360,6 +360,10 @@
## Code Health
+* [Update taproot detection](https://github.com/lightningnetwork/lnd/pull/10683)
+ to accommodate buried activation (and modified RPC `getdeploymentinfo`
+ response) beginning in Bitcoin Core v32.
+
## Tooling and Documentation
* [Added missing `lncli:` tags](https://github.com/lightningnetwork/lnd/pull/10658)
@@ -382,6 +386,7 @@
* Erick Cestari
* Gijs van Dam
* hieblmi
+* Matthew Zipkin
* Mohamed Awnallah
* Nishant Bansal
* Pins
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.