From 33700c8358a40503b5426a78a1daeba533d43d23 Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Wed, 17 Jun 2026 08:34:34 -0700 Subject: [PATCH] chore: re-version to v0.42.51.0 (natural next-off-master) Maintainer override of the queue allocator's leap to 0.44.1.0 (it jumped past in-flight sibling PR claims at 0.42.50/0.43.0/0.44.0). Take the natural next slot in the 0.42.x line above the immediate sibling claim (0.42.50.0); a merge re-bump resolves any collision if a cathedral PR lands first. Co-Authored-By: Claude Opus 4.8 (1M context) --- CHANGELOG.md | 4 ++-- VERSION | 2 +- package.json | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index ce69e2868..c35bc0f6a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,7 @@ All notable changes to GBrain will be documented in this file. -## [0.44.1.0] - 2026-06-17 +## [0.42.51.0] - 2026-06-17 **`gbrain sync` stops bottlenecking all its workers on a single database row, a malformed checkpoint can no longer wedge a source, and `gbrain doctor` tells an actively-running sync apart from a stuck one.** A slow source that fell behind HEAD could read as permanently stale even while it imported every cycle: sync was single-core-bound at the database layer, so handing it more workers didn't help, and the freshness check couldn't see that a sync was in fact running. @@ -16,7 +16,7 @@ The root cause was the page-generation clock that backs the search cache. Every - **A malformed checkpoint record can no longer wedge a source.** Checkpoint state is structurally constrained, repaired automatically on upgrade, and the loader survives a bad record instead of discarding all banked progress for that source. - **`gbrain sync --force-break-lock` is honest when there is no lock.** It now says plainly that nothing was held and points at how to inspect a genuinely wedged sync, instead of a terse no-op that read like a successful unwedge. -### To take advantage of v0.44.1.0 +### To take advantage of v0.42.51.0 `gbrain upgrade`, then `gbrain doctor`. Existing brains pick up the contention-free clock and the checkpoint integrity constraint automatically on the next migration; the search cache rebuilds itself on first query. Nothing to configure. ## [0.42.49.0] - 2026-06-16 diff --git a/VERSION b/VERSION index 88f59d655..6a6c1a02a 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.44.1.0 +0.42.51.0 diff --git a/package.json b/package.json index 0db9ee1b8..82b43c3bc 100644 --- a/package.json +++ b/package.json @@ -143,5 +143,5 @@ "bun": ">=1.3.10" }, "license": "MIT", - "version": "0.44.1.0" + "version": "0.42.51.0" }