Bump version to 1.2.1 - #5
Merged
Merged
Conversation
The v1.2.0 tag predates the release workflow, so it cannot dispatch the workflow that would publish it, and the pypi environment only permits v* tags to deploy. Rather than move a published tag or loosen that policy, cut 1.2.1 from a commit that contains the release machinery releasing it. The package is byte-identical to 1.2.0: src/ and pyproject.toml are unchanged between the two tags. Only the release workflow, docs and tests differ, and the changelog says so plainly so nobody hunts for a behavior change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0114gUUe4CxYr8W8oC95ffmD
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.
The v1.2.0 tag predates the release workflow, so it cannot dispatch the
workflow that would publish it, and the pypi environment only permits v* tags
to deploy. Rather than move a published tag or loosen that policy, cut 1.2.1
from a commit that contains the release machinery releasing it.
The package is byte-identical to 1.2.0: src/ and pyproject.toml are unchanged
between the two tags. Only the release workflow, docs and tests differ, and
the changelog says so plainly so nobody hunts for a behavior change.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_0114gUUe4CxYr8W8oC95ffmD