Repository navigation
revert: move file format v8 (#377) from main to the v3 branch - #378
Merged
Merged
Conversation
Main must stay releasable as v2.x so v2.1–v2.3 (and #370's unreleased fix) can ship without a forced one-way format migration. The v8 work (#371, #287) is preserved unchanged on the long-lived `v3` branch (at b8a9762), which will merge main regularly and becomes main when v3.0.0 is cut. This reverts commit b8a9762. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BedF9ZmqVZLkvDwn91fuKy
This was referenced Sep 25, 2026
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This was referenced Sep 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6545
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Moves the file-format-v8 work from #377 off
mainand onto a long-livedv3branch, somainstays releasable as v2.x.v3was pushed atb8a9762, the fix!: file format v8 — keep same-transaction multi-valued facts (#371, #287) #377 merge commit, so the v8 work is kept unchanged there.b8a9762onmain. The resulting tree is identical to84bf375(git diff 84bf375 HEADis empty).Why
With #377 on
main, the next release cut frommainwould have to be v3.0.0. That would block v2.1–v2.3 (#241, #185, #306, #310, #316, #323, #315) and the unreleased #370 fix (#372) from shipping without the one-way v7→v8 migration.Branch policy going forward
mainis the v2.x line. v2.1–v2.3 and any v2.0.x patches (including fix: derive FactRefs from on-disk layout when rebuilding indexes on open (#370) #372) ship from here.v3carries the v3.0.0 work (fix!: file format v8 — keep same-transaction multi-valued facts (#371, #287) #377, and Add index integrity check (verify) and public rebuild-indexes-from-fact-pages #373–docs: selective_fact_fetch doc comment omits valid_from/valid_to from dedup key #376, post-1.0: add lag/lead window functions #182, post-1.0: add sliding row frames for window functions #183, Expose UDF registration in every binding #180–post-1.0: expose PreparedQuery over UniFFI #181, feat(ffi): expose OpenOptions over UniFFI — the close-time checkpoint cannot be suppressed from Python #322, research: temporal graph traversals (temporal network analysis) #273). It mergesmainregularly, and PRs for v3.0.0 issues targetv3. At the v3.0.0 cut,v3merges intomain.v3and ship in v3.0.0. v2.x keeps the documented workaround: one multi-valued fact per transact.🤖 Generated with Claude Code
https://claude.ai/code/session_01BedF9ZmqVZLkvDwn91fuKy