From 5bde500cf95ac748949b349c3566a97cbb8f3050 Mon Sep 17 00:00:00 2001 From: Lakshman Patel Date: Fri, 12 Jun 2026 17:57:17 +0530 Subject: [PATCH] docs: clarify duplicate 0.1.0 changelog headings are pre/post-rebase The CHANGELOG contained two [0.1.0] sections with different dates (2026-04-28 and 2026-05-12), with the [0.3.0] 2026-05-01 sitting between them. The reverse-chronological order was correct, but the duplicate version heading was confusing. Add a note to the older [0.1.0] 2026-04-28 section explaining that it is the original pre-rebase initial release and that a later patch release reused the same 0.1.0 version after the eco-wide version re-baseline. --- CHANGELOG.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 187d6b1..73713db 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -114,6 +114,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Initial Release +> Note: this is the original initial release, dated 2026-04-28. A later patch +> release with the same `0.1.0` version was tagged on 2026-05-12 (above); the +> duplicate version heading predates the eco-wide version re-baseline that +> collapsed the interim `0.3.0` line into the current `0.1.0`. + **Core** - Relaxed DAG memory graph (Labeled Property Graph in SQLite) - 9 coding-specific node types: convention, decision, bug, spec, task, skill, preference, file, entity