Resolve the release-policy finding: 2.2.0's PyPI release was intentional - #154
Merged
Conversation
The prior audit (PR #153) left one finding unfixed: README's Roadmap section claimed "only 2.0.0 was an actual PyPI release," which PyPI itself contradicts (2.2.0, a minor version, is also published there). That was deliberately left as a process question for the maintainer rather than a wording fix -- confirmed intentional. Updates README's roadmap table (2.2.0 now carries the same "released" marker 2.0.0 has) and prose (states what actually happened instead of a policy that wasn't held to: 2.1.0/1.3.1/1.4.0's work folded into 2.0.0 and 2.2.0's releases rather than shipping separately, but both 2.0.0 and 2.2.0 themselves were released directly, contradicting the original major-version-only policy). Issue #107, the source both README and docs/CLAIMS.md draw the roadmap narrative from, gets the same correction: its stated release policy line now carries a dated note recording what actually happened, rather than silently rewriting the historical record. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RzqEV89zgdGLb3QgnZy3vp
4 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
2 participants
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
PR #153's audit left one of its seven findings deliberately unfixed: README's Roadmap section claims "per the roadmap's own release policy, only 2.0.0 was an actual PyPI release," which is contradicted by PyPI itself (2.2.0, a minor version, is also published there — plus five earlier minor/patch versions). That PR left it for a maintainer decision rather than rewriting the prose, since the real question was whether 2.2.0's publication was intentional. Confirmed: it was. This PR applies the resulting fix.
What's included
docs/CLAIMS.mddraw this roadmap narrative from): updated its stated release-policy line with a dated correction note recording what actually happened, and marked 2.2.0's table row as released — rather than silently rewriting the historical record of what the policy originally said.Verification
uv run --frozen pytestpassesuv run --frozen ruff check .anduv run --frozen ruff format --check .are cleanuv run --frozen mypyis clean (strict)CHANGELOG.mdhas an entry under## [Unreleased]src/touched, no behavior change.Notes
Follow-up to #153, which left this exact question open. Not tied to a tracking issue.
🤖 Generated with Claude Code
https://claude.ai/code/session_01RzqEV89zgdGLb3QgnZy3vp
Generated by Claude Code