Release 0.7.3 for the changelog consolidation - #8
Merged
Merged
Conversation
Bumps the version so v0.7.3 describes an artifact that reports itself as 0.7.3. Tagging the previous commit as v0.7.3 would have left the tag pointing at a tree declaring 0.7.2, so building from the tag would produce tappay-0.7.2 files: the same tag/artifact mismatch that made 0.7.2 a new version rather than a re-cut 0.7.1. The change being released is the CHANGES.md removal and the migration of the 0.2.0, 0.3.0 and 0.4.0 entries into CHANGELOG.md. CHANGELOG.md ships in the source distribution, so sdist contents genuinely differ from 0.7.2. No library code has changed since 0.7.1. Co-Authored-By: Claude Opus 5 <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
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.
Documentation only. No library code has changed since 0.7.1.
Releases the
CHANGES.mdremoval and the migration of the 0.2.0, 0.3.0 and0.4.0 entries into
CHANGELOG.md(#7).Why a version bump rather than just a tag
CHANGELOG.mdships in the source distribution, so sdist contents genuinelydiffer from 0.7.2 — this is a packaging change, not purely a repo change.
More importantly, tagging the previous commit as
v0.7.3would have left thetag pointing at a tree that declares
version = "0.7.2". Anyone building fromv0.7.3would gettappay-0.7.2files, andtappay.__version__would report0.7.2. That is the same tag/artifact mismatch that made theMANIFEST.infixa new 0.7.2 instead of a re-cut 0.7.1, so it gets the same treatment here.
Tag status
v0.7.1andv0.7.2are both tagged but unpublished — nothing in this line hasreached PyPI yet. If 0.7.3 is the version you publish, those two simply remain
points in history, which is normal and needs no cleanup.
🤖 Generated with Claude Code