chore: widen attune-rag pin to <0.3 and release v0.14.1#43
Merged
Conversation
attune-rag 0.2.0 shipped 2026-05-25 as the first SemVer-binding cut — purely additive (new measure_corpus module + aliases helpers; no breaking API changes). The current [rag] extra pin caps at <0.2, silently locking installs to attune-rag 0.1.23 even when 0.2.x is available. Widen the cap to <0.3 so `pip install attune-author[rag]` resolves attune-rag 0.2.x while still requiring explicit re-validation for the next breaking minor. Local smoke (python 3.10, fresh venv): pip install -e .[rag] → attune-author 0.14.1, attune-rag 0.2.0 53/53 rag- and faithfulness-marked tests pass. No code changes — RagPipeline / DirectoryCorpus / FaithfulnessConfig surfaces consumed by rag_hook.py and faithfulness/ are unchanged across the 0.1.x → 0.2.0 bump.
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-ragpin in the[rag]extra from<0.2to<0.3so installs ofattune-author[rag]pick up the freshly-released attune-rag 0.2.0 (first SemVer-binding cut, purely additive).RagPipeline/DirectoryCorpus/FaithfulnessConfig/JudgeOutcomesurfaces consumed byattune_author.rag_hookandattune_author.faithfulnessare unchanged across the 0.1.x → 0.2.0 bump (verified by smoke-installing locally and running the 53 rag/faithfulness tests).Test plan
pip install -e .[rag]resolvesattune-rag 0.2.0(was capped at 0.1.23)rag_enabled()returnsTrue;RagPipeline,DirectoryCorpusimport cleanly[rag]-extra coverage intests.yml— pin widening verified locally)Release notes
After merge, tag
v0.14.1and push to triggerpublish.yml(trusted publishing, environmentpypi).