Repository navigation
release: cut 1.0.0-rc.78 - #1052
Merged
Merged
Conversation
The index-size stage-1 and corpus-packs release: 28 PRs over the rc.77 window (v1.0.0-rc.77..main @ 044e6c6). No tag pushed with this commit - the cut (tag + release PR + merge) is held for maintainer go, per directive 2026-09-29. CHANGELOG: [Unreleased] -> [1.0.0-rc.78] - 2026-09-29, fresh [Unreleased] above. The section was rich but 11 of the 28 window PRs were uncited - the release-notes gate (#474) would have failed its coverage check, the exact drift rc.77 dodged by being cut directly on main. Added: PR citations for the four size-epic format PRs that cited only epic #1038 (ZNV2 #1040, ZPS2 #1041, ZBS4 #1042, ZFM5 #1043); the three pack-publish hardening PRs folded into the corpus-pack entry's citation parenthetical (#1049 draft-then-publish mechanics, #1050 dated per-build-day tags, #1051 the loose <pack>-SHA256SUMS.sig release asset the zip consumer flow needs); new Documentation entries for the rc.19-rc.70 backfill (#1035), the ROADMAP 2026-09-26 review (#1036), the stage-1 blog post (#1044) and the corner-brand/blog-endings site work (#1045). One honesty fix from the entry verification pass: ZFM5's "every other extension byte-identical" gains its 3 B .jsonl state-noise exception (measured 3,256 -> 3,259 B between the committed controls). ROADMAP: release-cut roll per the docs_capability_lists contract - Next release -> rc.79, review line -> 2026-09-29 against rc.78, riding-to list folded into the rc.78 cut record, open defects carried into rc.79 (#1031, #1032, live-verified open at the cut via the tracker API). Tracker #298 closed as abandoned (2026-09-29): the review cadence is machine-enforced by docs_capability_lists, not by the issue; its link - and the closed #941/#874 links - are removed from the open-defects shortlist, where the release-notes gate's check 1a requires every issues/N link to be open. Version: engine/Cargo.toml 1.0.0-rc.77 -> 1.0.0-rc.78 (the [workspace.package] version, 17 crates inherit; Cargo.lock refreshed via cargo metadata - diff is exactly the 17 member version lines); 89 landing release stamps V1.0.0-RC.77 -> V1.0.0-RC.78 (88 footer/print stamps across 52 pages + the data-latest-tag literal at landing/index.html:178; the dated tokens stay per the rc.77 release precedent). Stamps and Cargo bump ship together so the landing-constants-guard allow-set {newest tag, tree version} holds on the release branch. Gates, run locally on this tree: release-notes-gate.sh PASS (freshness, shortlist state, 5 Fixed citations closed, 28/28 window PRs cited); landing-constants-guard all green; docs_capability_lists 15 passed / 0 failed (includes the two roadmap-freshness tests that pin this roll). Engine code untouched - ES-YAML conformance surface unchanged by this commit.
The Technical SEO gate failed on PR #1052 at gen_sitemap.py --check: landing/sitemap.xml is generated, not hand-edited. The 89 V1.0.0-RC.78 stamp edits touch 52 pages, so their lastmod moves to 2026-09-29; regenerated with gen_sitemap.py --write - the diff is exactly those 52 lastmod lines and nothing else. All eight seo.yml checks pass locally after the regen (test_article_schema, build_articles/gen_sitemap/ fix_heads/fix_links/mk_og_card --check, seo_lint, audit).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Release PR for v1.0.0-rc.78 — the index-size stage-1 and corpus-packs release: 28 PRs over the rc.77 window (
v1.0.0-rc.77..main@f82118bd0). rc.77 dodged this gate by being cut directly on main; this one goes through the PR so the release-notes gate runs in CI.Single commit
736cc5317, gates all green locally before the push:[Unreleased]→[1.0.0-rc.78] - 2026-09-29with a fresh[Unreleased]above. All 11 previously-uncited window PRs now cited: PR refs for the four size-epic format PRs that cited only epic engine: reduce on-disk index size — per-block bitpacking, delta encodings, one shared term dictionary, zstd trained dictionaries #1038 (ZNV2 storage: bit-pack .dv numeric columns (ZNV2 — FOR + GCD + 128-doc blocks) #1040, ZPS2 perf(fts): ZPS2 .post block framing — derived lengths, width-0 constants, banded FOR, freq elision #1041, ZBS4 storage: ZBS4 stored-section slim — typed ints, copy-of refs, merge-path zstd chooser (epic #1038 stage 1) #1042, ZFM5 fts: ZFM5 meta records — columnar varint streams under the zstd envelope (epic #1038) #1043); ci(pack-publish): publish under immutable releases — drop, draft, publish #1049/ci(pack-publish): dated daily releases — immutable-release tags are single-use #1050/fix(autoindex): corpus add --verify-sig finds the loose release sig beside a pack zip #1051 folded into the corpus-pack entry's citation parenthetical; new Documentation entries for docs(changelog): reconstruct the rc.19–rc.70 gap (GA gate item) #1035 (changelog backfill), docs(roadmap): roll forward to 2026-09-26 — the stale-evening corrections + rc.78 queue #1036 (ROADMAP 2026-09-26 review), blog: stage-1 index-size write-up — Cutting the index 28% #1044 (stage-1 blog post), site: corner brand XERJ (not XERJ.AI) everywhere; blog posts end on conclusions + try-it #1045 (corner brand + blog endings). One honesty fix from the entry-verification pass: ZFM5's "every other extension byte-identical" gains its 3 B.jsonlstate-noise exception.docs_capability_listscontract: Next release → rc.79, review line → 2026-09-29 againstv1.0.0-rc.78, riding-to list folded into the rc.78 cut record, open defects carried into rc.79 (autoindex: a source file that grows mid-run (append-only log) kills the run, is misclassified as a bulk/backend failure, and the retry advice points at the wrong fix #1031, engine: stored_value_cache / dv_cache / id_pos_cache remain unbounded until merge-retire — the residual heap-per-doc retention after #1002 #1032 — live-verified open at the cut). Tracker 📍 XERJ public roadmap — where the project is going and how to follow it #298 was closed as abandoned today (2026-09-29); its link and the closed Tracking: the zero-token direction, stage 1 — rerank stage, share links + reading room, mbox/Takeout ingest, autoindex resilience #941/Meta: idle cost must be near-zero on dev laptops — the reference-coding resource budget (#871 #872 #873) #874 links are removed from the open-defects shortlist, where gate check 1a requires everyissues/Nlink to be open.engine/Cargo.toml→1.0.0-rc.78(workspace package, 17 crates inherit;Cargo.lockrefreshed viacargo metadata, diff is exactly the 17 member version lines) + 89 landing release stamps (V1.0.0-RC.77→V1.0.0-RC.78: 88 footer/print stamps across 52 pages + thedata-latest-tagliteral; dated tokens untouched per the rc.77 precedent).Local gate results:
release-notes-gate.shPASS (freshness, shortlist state, 5 Fixed citations closed, 28/28 window PRs cited);landing-constants-guard.shall green;docs_capability_lists15 passed / 0 failed. Engine code untouched — ES-YAML surface unchanged.After merge: tag
v1.0.0-rc.78lands on the merge commit; the Release workflow publishes the GitHub Release with the cross-target binaries.🤖 Generated with Claude Code