release: v7.1.2 — widen attune-rag pin to <0.3#465
Merged
Conversation
attune-rag 0.2.0 shipped 2026-05-25 as the first SemVer-binding
cut — purely additive (new measure_corpus module + aliases-file
helpers; no breaking API changes). The current core pin caps at
<0.2, silently locking fresh installs of attune-ai to
attune-rag 0.1.23 even when 0.2.x is available.
Widen the core pin AND the [dev] extra's test-coverage pin to
<0.3 so `pip install attune-ai` resolves attune-rag 0.2.x.
Local smoke (uv sync --extra dev in the .venv):
- attune-ai 7.1.2, attune-rag 0.2.0 resolved cleanly
- All four import paths used by attune-ai work:
from attune_rag import RagPipeline
from attune_rag.corpus.directory import DirectoryCorpus
from attune_rag.pipeline import RagPipeline
from attune_rag.provenance import format_citations_markdown
- 137/137 attune_rag-importing tests pass (3 xfails are
pre-existing structural ceilings, not regressions)
No code changes — RagPipeline / DirectoryCorpus /
format_citations_markdown surfaces consumed by
attune.workflows.rag_code_gen, attune.memory.personal, and
attune.mcp.workflow_handlers are unchanged across 0.1.x -> 0.2.0.
Companion comment block at the bottom of pyproject.toml updated
to match for accuracy.
uv.lock regenerated for the bump (lockfile drift was minimal:
attune-ai 7.1.1 -> 7.1.2, attune-rag 0.1.5 -> 0.2.0, plus two
existing transitive deps newly attributed to attune-rag).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
documentation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.3(and matching widen in the[dev]extra's test-coverage pin) so freshpip install attune-aipicks up the freshly-released attune-rag 0.2.0 (first SemVer-binding cut, purely additive).uv.lock.RagPipeline/DirectoryCorpus/format_citations_markdownsurfaces consumed byattune.workflows.rag_code_gen,attune.memory.personal, andattune.mcp.workflow_handlersare unchanged across attune-rag 0.1.x → 0.2.0.Test plan
uv sync --extra devresolvesattune-rag 0.2.0(was capped at 0.1.5)v7.1.2(push triggerspublish-pypi.yml)Companion releases
This is the third in a coordinated set widening the attune-rag pin across the downstream family. Companions: