Skip to content

Commit c4519dd

Browse files
release: v0.8.0 — widen attune-rag pin + ship pending MCP work (#64)
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).
1 parent 502bdbd commit c4519dd

2 files changed

Lines changed: 24 additions & 2 deletions

File tree

CHANGELOG.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,28 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
55

66
## [Unreleased]
77

8+
Work in progress for the next release. Add entries here as
9+
changes land, not at tag time.
10+
11+
## [0.8.0] — 2026-05-25
12+
13+
Bundles the MCP server work (Phases 1–5, completed across PRs #49#56) with the spec-status parser fix (PR #57), the living-docs regen automation Phase 1 (PRs #60, #61, #62, #63), the home interpreter snapshot improvement (PR #59), the stacked-rebase README note (PR #58), and a routine `attune-rag` cap widen to admit the freshly-released 0.2.0. Triggered by the cap widen — the rest had been queued on `main` waiting for a release.
14+
15+
### Changed
16+
17+
- **Widen `attune-rag` core pin: `>=0.1.22,<0.2`
18+
`>=0.1.22,<0.3`.** Unblocks fresh installs of `attune-gui`
19+
alongside [attune-rag 0.2.0](https://pypi.org/project/attune-rag/0.2.0/)
20+
(released 2026-05-25 as the first SemVer-binding cut — purely
21+
additive: new `attune_rag.measure_corpus` public module + new
22+
`load_aliases_from_file` / `DirectoryCorpus(extra_aliases_file=...)`).
23+
None of the `attune_rag` surfaces consumed by `attune_gui`
24+
(`RagPipeline`, `DirectoryCorpus`, `QueryExpander`,
25+
`attune_rag.editor.*`) changed across 0.1.x → 0.2.0, so this
26+
is a pin widen only with no code changes. Cap raised one minor
27+
rather than open-ended so the next breaking attune-rag bump
28+
still requires explicit re-validation.
29+
830
### Fixed
931

1032
- **`**Status:**` (colon-inside-asterisks) format now parses

pyproject.toml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
44

55
[project]
66
name = "attune-gui"
7-
version = "0.7.1"
7+
version = "0.8.0"
88
description = "Local dashboard for attune-rag / attune-help / attune-author. Server-rendered Jinja2 UI — ships clean via PyPI with no npm step."
99
readme = "README.md"
1010
requires-python = ">=3.10"
@@ -29,7 +29,7 @@ dependencies = [
2929
"uvicorn[standard]>=0.27,<1.0",
3030
"pydantic>=2.0,<3.0",
3131
"structlog>=24.0,<26.0",
32-
"attune-rag>=0.1.22,<0.2",
32+
"attune-rag>=0.1.22,<0.3",
3333
"attune-author[ai]>=0.14.0,<0.15",
3434
"attune-help>=0.10.0,<1.0",
3535
"jinja2>=3.1,<4.0",

0 commit comments

Comments
 (0)