release: v0.7.0 — ship relocated authoring modules; drop attune-help dep#15
Merged
Conversation
PR #14 (B1 of architecture-realignment) inverted the manifest / staleness / freshness relocation: those modules now live natively in attune-author. This release packages that change and removes the leftover ``attune-help>=0.10.0`` runtime dependency, which was only there because attune-author used to re-export from attune-help. There are no remaining ``from attune_help`` imports in ``src/attune_author/``. Side effect: this also unblocks attune-help 0.11.0 (B2 shim PR #6), which declares ``attune-author>=0.7.0`` for its deprecation shims. Without this release the two packages would form a circular package-metadata edge. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Three ruff failures inherited from PR #14's merge (the relocated content was previously in attune-help, which had different line- length tolerance): - src/attune_author/staleness.py: 107-char comment in docstring example wrapped across two lines. - tests/test_staleness_relocated.py: 107-char string literal in test data split into three concatenated string parts. - tests/test_manifest_relocated.py: import block reordered (ruff --fix). Folded into the 0.7.0 release PR so CI can pass and the release tag can be cut. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
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
manifest/staleness/freshnessnow live natively inattune-author.attune-help>=0.10.0. It was a leftover from when those modules were re-exported from attune-help; now that the relocation is inverted, nofrom attune_helpimports remain insrc/attune_author/.__version__to 0.7.0.Why now
Two reasons converge:
attune_author.manifest/staleness/freshnessfrom PyPI today gets nothing.attune-author>=0.7.0for its deprecation shims. That PR can't be merged until 0.7.0 exists. Cutting this release unblocks B2 — and incidentally avoids a circular package-metadata edge (attune-author -> attune-help -> attune-author) once attune-help 0.11.0 ships.Test plan
--ignore=tests/test_mcp_server.pybecause the venv lacks themcpoptional extra; CI runs the full matrix).v0.7.0, push tag, verify thepypienv publish workflow promotes to PyPI before merging attune-help#6.🤖 Generated with Claude Code