chore: bump to 0.9.1 and remove CHANGELOG.md#594
Merged
Conversation
0.9.0 is already published on PyPI, so the next release must build a higher version or the publish step is rejected as a duplicate. Bump pyproject.toml + uv.lock to 0.9.1 (via `uv version`) so cutting a 0.9.1 GitHub Release publishes cleanly. Also remove CHANGELOG.md: release notes are maintained in GitHub Releases, the file was stale (newest dated entries were 0.2.x), and nothing references it. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
What
pyproject.toml+uv.lock(viauv version, matching the CI bump job'suv version --offline).CHANGELOG.md.Why bump
0.9.0is already published on PyPI and the repo'spyproject.tomlwas still pinned at0.9.0.publish.ymlbuilds frompyproject.tomlonrelease: published, so cutting a release now would try to upload a duplicate0.9.0and PyPI would reject it. Setting0.9.1lets a0.9.1GitHub Release publish cleanly. After that publish, the existing post-publishbump-versionjob will auto-increment to0.9.2as usual.Why remove the changelog
Release notes are maintained in GitHub Releases.
CHANGELOG.mdwas stale (newest dated entries were0.2.x) and nothing references it (no docs build, packaging, or workflow), so removing it is safe.Scope
Release-prep only — no source/behavior changes. Kept separate from the feature PR (#593) so it can merge independently right before a release.
🤖 Generated with Claude Code