What changed, and why it matters
This commit only adds a new section to the RELEASE-NOTES.md file describing version 0.12.0. It lists user-visible changes such as a new indexing dependency, API fixes, a new SECURITY.md file, and routine dependency updates. No program code was changed, so this commit by itself cannot introduce, fix, or exploit a security vulnerability.
No security action needed for this commit. Review the actual code changes referenced in the changelog (e.g., `server.features` fix, `transaction.id_from_pos` parsing, dependency updates, and the new SECURITY.md) separately if assessing the 0.12.0 release's security posture.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to RELEASE-NOTES.md. It records the 0.12.0 release notes, including a switch to bindex (requiring Bitcoin Core 31+ and index rebuild), server.features response format fix, transaction.id_from_pos argument parsing update, addition of SECURITY.md, and dependency bumps. There are no source-code modifications, build system changes, or configuration changes.
Changed components
RELEASE-NOTES.mdInspect captured patch +8 / −0
### RELEASE-NOTES.md
@@ -1,3 +1,11 @@
+# 0.12.0 (Sep 13 2026)
+
+* Switch to `bindex`: requires Bitcoin Core 31+ and rebuilding the index.
+* Fix `server.features` response format.
+* Update `transaction.id_from_pos` argument parsing for API compliance.
+* Add `SECURITY.md`.
+* Update dependencies (`bitcoin`, `bitcoin_slices`, `bytes`, `crossbeam-channel`, `ctrlc`, `log`, `rayon`, `serde_json`, `signal-hook`, `tempfile`).
+
# 0.11.1 (Feb 22 2026)
* Update `transaction.id_from_pos` response for API compliance.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.