Correct CHANGELOG dates on 0.2.1 and 0.2.2
What the developer wrote
Authored by Matt Corallo
Correct CHANGELOG dates on 0.2.1 and 0.2.2
What changed, and why it matters
This commit only fixes two release dates in the project's CHANGELOG.md file, changing the years for versions 0.2.1 and 0.2.2 from 2025 to 2026. There are no code changes, no security fixes, and no functional impact.
No security action needed. This is a documentation-only metadata correction.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies only CHANGELOG.md, correcting the release date years for versions 0.2.2 (‘Feb 6, 2025’ to ‘Feb 6, 2026’) and 0.2.1 (‘Jan 29, 2025’ to ‘Jan 29, 2026’). No source code, build files, tests, or documentation beyond the changelog are touched.
Changed components
CHANGELOG.mdInspect captured patch +2 / −2
diff --git a/CHANGELOG.md b/CHANGELOG.md
index b49b0d1..fca3bcf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -195,7 +195,7 @@ Thanks to Project Loupe for reporting most of the issues fixed in this release.
Thanks to Project Loupe for reporting most of the issues fixed in this release.
-# 0.2.2 - Feb 6, 2025 - "An Async Splicing Production"
+# 0.2.2 - Feb 6, 2026 - "An Async Splicing Production"
## API Updates
* The `SplicePrototype` feature flag has been updated to refer to feature bit
@@ -212,7 +212,7 @@ Thanks to Project Loupe for reporting most of the issues fixed in this release.
message from a peer was fixed (#4383).
-# 0.2.1 - Jan 29, 2025 - "Electrum Confirmations Logged"
+# 0.2.1 - Jan 29, 2026 - "Electrum Confirmations Logged"
## API Updates
* The `AttributionData` struct is now public, correcting an issue where it was
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.