Repository navigation
Release 0.2.0 - #15
Merged
Merged
Conversation
Bumps __version__ and files the Unreleased changelog entries under 0.2.0, as the README's release steps ask before tagging. The v0.2.0 tag made from the releases page pointed at a commit still saying 0.1.0, so the Release workflow stopped at its first gate and published nothing; PyPI still has only 0.1.0. The README's health-check example shows the new version too, since the README is also the PyPI page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FtCFQJ6wEFf5pZSL2HSE8G
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.
What changes
__version__goes from 0.1.0 to 0.2.0.## [0.2.0] - 2026-10-16and updates the links at the bottom.Why
The v0.2.0 release was published from the releases page on c7f6c75, which still said 0.1.0. So the Release workflow stopped at its first gate, both times it ran: "tag v0.2.0 does not name the packaged version 0.1.0". The README's release steps bump the version through a PR before tagging. Nothing was published: PyPI has only 0.1.0, so 0.2.0 is still free.
After merging
The v0.2.0 tag still points at c7f6c75. Once this merges, I'll delete it and tag the merge commit, which runs the Release workflow again. GitHub turns a release into a draft when its tag is deleted, so the v0.2.0 release page may need publishing again afterwards.
Testing
GITHUB_REF_NAME=v0.2.0:release.yml, passes, and still refuses a version the changelog doesn't name;twine check --strictpasses on the sdist and the wheel.pasteup 0.2.0, and passes all 194 tests.🤖 Generated with Claude Code
https://claude.ai/code/session_01FtCFQJ6wEFf5pZSL2HSE8G
Generated by Claude Code