release: v1.4.0 - #185
Merged
Merged
Conversation
robotrocketscience
added a commit
that referenced
this pull request
Apr 28, 2026
The 'Versions at a glance' table marked v1.3.0 and v1.4.0 as planned, and the body still listed them under the 'Planned' section, despite v1.3.x retrieval-wave commits and the v1.4.0 release tag (#185, 2026-04-28) being on main. README's roadmap table already showed both as shipped, so README and docs/ROADMAP.md disagreed. - Table: flip v1.3.0 and v1.4.0 to shipped, fold the README's more specific wording back into ROADMAP for consistency. - Body: move v1.3.0 and v1.4.0 subsections out of '## Planned' into the end of '## What shipped'; tighten verbs to past-tense; relink the dynamic-trigger revisit to the live tracker (#188 instead of the resolved #141 closer); point the full-posterior eval at v1.6.0/#151 (the new home per the v1.5/v1.6/v1.7 split) rather than v2.0 directly. - v1.2.x search-tool hook stays in Planned (still unshipped; #155 is the v1.5 follow-up).
6 tasks
robotrocketscience
added a commit
that referenced
this pull request
Apr 28, 2026
…1.6; fix #141→#188 (#230) ## Summary - v1.5 roadmap line: annotate #148 (BM25F) as merged on main (commit 86c62b5); correct dynamic-trigger revisit ref from stale #141 to #188. - v1.6 roadmap line: add #216 (Plate FFT HRR primitives), relabeled v1.5 → v1.6 since it's an HRR prereq for #152, which sits on v1.7. - #204 stays on v1.5: its schema (`belief_versions` / `edge_versions` + `version_vector_backfill_complete` marker) is already merged on `main` under the v1.5.0 banner per the in-source comments; remaining backfill is the v1.5 work that keeps the issue open. - **Expanded:** sync `docs/ROADMAP.md` to reflect that v1.3.0 and v1.4.0 actually shipped. README's roadmap table already showed both as shipped (release tag #185 landed 2026-04-28); ROADMAP's "Versions at a glance" table and "Planned" section still listed them as planned. Move the v1.3 and v1.4 subsections from "Planned" to "What shipped", tighten verbs to past-tense, and relink the dynamic-trigger revisit (#141 → #188). Originally moved #204 to v1.6 alongside #216 in the issue-label sweep; reverted after spotting that the schema had already shipped. ## Test plan - [x] README v1.5 line shows `#148, merged` and `#188` - [x] README v1.6 line includes `#216` - [x] docs/ROADMAP.md v1.6 row shows the HRR primitives addition; v1.5.0 section bullet for #148 marked merged; dynamic-trigger bullet links #188 - [x] docs/ROADMAP.md "Versions at a glance" marks v1.3.0 and v1.4.0 as shipped - [x] docs/ROADMAP.md v1.3.0 and v1.4.0 subsections live under "What shipped", not "Planned" - [ ] No code changes; CI staging-gate need not gate this beyond the docs jobs
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.
Summary
Cuts v1.4.0 — the context rebuilder (PreCompact retrieval-curated continuation) plus the v1.3 retrieval wave (entity index, BFS multi-hop, opt-in LLM-Haiku classifier, partial Bayesian-weighted ranking). Companion fixes, CI work, and docs polish ship in the same tag.
Headline features
rebuild_v14()(#139); manual + threshold trigger modes (dynamic parked v1.5) (#141); continuation-fidelity scorer (exactmethod) (#138); eval-harness scaffolding (#136).aelf project-warm(#137);aelf session-delta --id(#140);aelf --advanced/aelf --help --advanced(#159).project-warmworktree sentinel (#161).Full detail: see CHANGELOG.md
## [1.4.0].Pre-flight
uv run pytest tests/ -x -q→ 1443 passed, 2 skipped locally.uv build→dist/aelfrice-1.4.0-py3-none-any.whlanddist/aelfrice-1.4.0.tar.gzclean.uv run aelf --help→ CLI surface matches expectation (rebuild, search, lock, locked, status, doctor, setup, onboard).uv run pyright src/→ 90 errors — pre-existing onmain(verified by revertingpyproject.toml+uv.lockand re-running). Not introduced by this release; tracked separately.What this PR does
Two atomic commits:
docs: soften Determinism section tone in README— replaces "Determinism is the property" with a quieter "Determinism" section per maintainer feedback.release: v1.4.0— bumpspyproject.tomlto1.4.0, regeneratesuv.lock, rotates CHANGELOG[Unreleased]→[1.4.0] - 2026-04-28, backfills the missing perf: shorten update-check TTL from 24h to 6h #172 / ci: reduce GitHub Actions burn (concurrency + dedup pytest + uv cache) #184 entries, updates the README roadmap to mark v1.3 / v1.4 as shipped, and adds the[1.4.0]link footnote.Tag plan
After merge:
git tag -s v1.4.0 -m "release: v1.4.0" && git push github v1.4.0. Tag push triggers.github/workflows/publish.yml; publish remains gated until v1.0.0 (already passed) — workflow now wired and will fire.