Repository navigation
Let a tag produce a GitHub release, not just a PyPI upload - #6
Merged
Merged
Conversation
Pushing v0.1.3 published the package and left the repository showing v0.1.2 as Latest, because a tag is not a release. The package was correct and the front page was a day out of date, which is the worst combination -- anybody checking the repo would have concluded the fixes had not shipped. The release job now writes the notes out of CHANGELOG.md for the tagged version and publishes them, after the upload succeeds. It fails loudly if the changelog has no section for that version, because a release with empty notes is worse than one that did not happen. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rv24tsMGnoTG7Hgrpeqg1V
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.
Pushing
v0.1.3published the package and left the repo showing v0.1.2 as Latest — a tag is not a release. The package was right and the front page was wrong, which is the worst combination: anyone checking the repo would have concluded the fixes had not shipped.The release job now extracts the notes from
CHANGELOG.mdfor the tagged version and publishes them, after the PyPI upload succeeds. It fails loudly if the changelog has no section for that version — a release with empty notes is worse than one that did not happen.Verified the extraction against the 0.1.3 section: 77 lines, starting at the right heading and stopping at the next one.
🤖 Generated with Claude Code