release: v0.8.0 — widen attune-rag pin + ship pending MCP work#64
Merged
Conversation
attune-rag 0.2.0 shipped 2026-05-25 as the first SemVer-binding cut — purely additive (new measure_corpus module + alias-file helpers; no breaking API changes). The current core pin caps at <0.2, silently locking fresh installs to attune-rag 0.1.23 even when 0.2.x is available. Widen the cap to <0.3 to unblock attune-rag 0.2.x installs. The cap widen is the trigger for promoting the pending [Unreleased] content to a real release. That content has been queued on `main` since v0.7.1 (2026-05-22): - MCP server Phases 1-5 (PRs #49-#56) — new attune-gui-mcp console script with 6 tools (5 read-mostly + gui_set_spec_status write); 30+ tests across test_mcp_tools.py and test_mcp_integration.py - **Status:** parser fix (PR #57) - Living-docs regen automation Phase 1 (PRs #60-#63) - Home interpreter snapshot (PR #59) - Stacked-rebase README note (PR #58) Bumped 0.7.1 → 0.8.0 (minor) for the new MCP tool surface. Local smoke (python 3.10, fresh venv): pip install -e .[dev] → attune-gui 0.8.0, attune-rag 0.2.0 545/545 sidecar tests pass (1 playwright skip, unrelated).
5 tasks
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
attune-ragcore pin from<0.2to<0.3so fresh installs ofattune-guipick up the freshly-released attune-rag 0.2.0 (first SemVer-binding cut, purely additive).[Unreleased]content as[0.8.0]— MCP server Phases 1-5 (PRs docs(specs): promote mcp-server-scope from gated draft to active #49-test(mcp): Phase 4 — integration tests (stacked on #55) #56), spec-status parser fix (fix(specs): _STATUS_VALUE_RE accepts both **Status**: and **Status:** #57), living-docs regen automation (spec: living-docs regen automation (CI fail-if-stale + make regen-all) #60-chore: remove redundant sidecar/.help/ corpus #63), home interpreter snapshot (feat(home): show probing interpreter on family snapshot #59), stacked-rebase README note (docs: README note on rebasing stacked PRs #58). All have been queued onmainsince v0.7.1 (2026-05-22) waiting for a release trigger; the cap widen is that trigger.RagPipeline/DirectoryCorpus/QueryExpander/attune_rag.editor.*surfaces are unchanged across the 0.1.x → 0.2.0 attune-rag bump.Test plan
pip install -e .[dev]resolvesattune-rag 0.2.0(was capped at 0.1.23)v0.8.0, push to triggerpublish.ymlNote on scope
The PR title says "release" because it cuts 0.8.0. The actual new work in this PR is a one-line pin widen; everything else has been on
mainfor days. If you'd rather hold the MCP work for a separate dedicated release, say the word and I'll split — but bundling matches the actual shipped binary and avoids a CHANGELOG/binary divergence.