Add CHANGELOG entries for 0.1.9 and 0.2.1
What the developer wrote
Authored by Matt Corallo
Add CHANGELOG entries for 0.1.9 and 0.2.1
What changed, and why it matters
This commit only adds release notes to the CHANGELOG.md file. It does not change any source code, so it cannot introduce or fix a security vulnerability by itself. The changelog text does mention prior bug fixes in earlier releases, but those changes are not part of this commit.
No action needed for this commit. Review the referenced pull requests separately if you want to assess the actual code changes they describe.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only addition to CHANGELOG.md describing releases 0.1.9 and 0.2.1. It lists API updates and bug fixes that were already merged in other commits (e.g., ElectrumSyncClient unconfirmed-transaction handling, splicing peer-feature checks, HTLC forwarding assertion). No executable code is modified.
Changed components
CHANGELOG.mdInspect captured patch +26 / −0
diff --git a/CHANGELOG.md b/CHANGELOG.md
index a51c5fd..6e83ef2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,29 @@
+# 0.2.1 - Jan 29, 2025 - "Electrum Confirmations Logged"
+
+## API Updates
+ * The `AttributionData` struct is now public, correcting an issue where it was
+ accidentally sealed preventing construction of some messages (#4268).
+ * The async background processor now exits even if work remains to be done as
+ soon as the sleeper returns the exit flag (#4259).
+
+## Bug Fixes
+ * The presence of unconfirmed transactions no longer causes
+ `ElectrumSyncClient` to spuriously fail to sync (#4341).
+ * `ChannelManager::splice_channel` now properly fails immediately if the
+ peer does not support splicing (#4262, #4274).
+ * A spurious debug assertion was removed which could fail in cases where an
+ HTLC fails to be forwarded after being accepted (#4312).
+ * Many log calls related to outbound payments were corrected to include a
+ `payment_hash` field (#4342).
+
+
+# 0.1.9 - Jan 26, 2026 - "Electrum Confirmations"
+
+## Bug Fixes
+ * The presence of unconfirmed transactions no longer causes
+ `ElectrumSyncClient` to spuriously fail to sync (#4341).
+
+
# 0.2 - Dec 2, 2025 - "Natively Asynchronous Splicing"
## API Updates
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.