docs: add 0.26.1 release notes to CHANGELOG and info.go
This commit is contained in:
11
CHANGELOG.md
11
CHANGELOG.md
@@ -7,7 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
## [0.26.0] - 2025-11-27
|
||||
## [0.26.1] - 2025-11-29
|
||||
|
||||
### Fixed
|
||||
|
||||
- **CRITICAL: Reverse ZFC Check (bd-53c)**: Prevents stale database from corrupting JSONL
|
||||
- Root cause: `bd sync` exports DB to JSONL before pulling from remote
|
||||
- If local DB is stale (fewer issues than JSONL), stale data would corrupt the JSONL
|
||||
- Added reverse ZFC check: detects when JSONL has >20% more issues than DB
|
||||
- When detected, imports JSONL first to sync database before any export
|
||||
- Prevents fresh/stale clones from exporting incomplete database state
|
||||
|
||||
## [0.26.0] - 2025-11-27
|
||||
|
||||
|
||||
@@ -287,6 +287,15 @@ type VersionChange struct {
|
||||
|
||||
// versionChanges contains agent-actionable changes for recent versions
|
||||
var versionChanges = []VersionChange{
|
||||
{
|
||||
Version: "0.26.1",
|
||||
Date: "2025-11-29",
|
||||
Changes: []string{
|
||||
"CRITICAL FIX (bd-53c): Reverse ZFC check prevents stale DB from corrupting JSONL",
|
||||
"bd sync now detects when JSONL has more issues than DB and imports first",
|
||||
"Prevents fresh/stale clones from exporting incomplete database state",
|
||||
},
|
||||
},
|
||||
{
|
||||
Version: "0.26.0",
|
||||
Date: "2025-11-27",
|
||||
|
||||
Reference in New Issue
Block a user