soulcraft/brainy
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases 335 Packages Wiki Activity Actions

docs: RELEASES.md entry for 8.0.14 (migration preserves branch-scoped non-entity state)

Browse source
This commit is contained in:
David Snelling 2026-07-07 16:07:10 -07:00
parent a93bb4e85f
commit 64188a33d4
1 changed files with 11 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
RELEASES.md
View file

@ -10,7 +10,17 @@ Full auto-generated changelog: `CHANGELOG.md` · Releases: https://github.com/so
--- ---
## v8.0.13 — 2026-07-07 (accurate boot log — established stores no longer report "New installation") ## v8.0.14 — 2026-07-07 (7→8 migration preserves branch-scoped non-entity state instead of deleting it)
Defense-in-depth for the one-time 7→8 layout migration. The migration rescues the head branch's
entities (`branches/<head>/entities/*` → `entities/*`) and then drained the whole `branches/<head>/`
directory. If a 7.x engine had written durable state under the head branch *outside* `entities/`
(a branch-scoped index, blob area, or field registry), that drain would have silently deleted it —
the same failure class as the VFS content blobs a 7.x store kept in `_cow/`. The migration now drains
the branch only when nothing but the moved entities remains; if any non-entity object survives, it
**preserves the branch** (no delete) and logs a loud warning naming the leftover keys, so the state is
recoverable rather than lost. No effect on a normal migration (a clean branch still drains); purely a
guard against silent data loss.
Cosmetic boot-log fix. Every persisted 8.0 store logged `📁 New installation: using depth 1 Cosmetic boot-log fix. Every persisted 8.0 store logged `📁 New installation: using depth 1
sharding` on **every** open — even established brains holding thousands of entities — which is sharding` on **every** open — even established brains holding thousands of entities — which is