Skip to content

Release 2.3.3: bump version and check tag matches version - #94

Merged
twalen merged 1 commit into
masterfrom
release-2.3.3
Oct 18, 2026
Merged

twalen merged 1 commit into
masterfrom
release-2.3.3

Conversation

@twalen

@twalen twalen commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

Fixes #93.

The v2.3.2 GitHub release was tagged while pyproject.toml still said 2.3.1, so the publish workflow built 2.3.1 again and PyPI rejected the upload (same thing happened with v2.3.0). Rather than moving the published v2.3.2 tag, this releases from master as 2.3.3, which also includes #92.

Changes:

  • Bump version in pyproject.toml to 2.3.3.
  • Add a step to release.yml that fails early if the release tag (minus the v prefix) doesn't match the version in pyproject.toml.

After merging: create a GitHub release with tag v2.3.3 on master to trigger the PyPI publish.

🤖 Generated with Claude Code

The v2.3.2 release was tagged with pyproject.toml still at 2.3.1, so the
publish workflow tried to re-upload 2.3.1 and PyPI rejected it. Add a
check that fails early when the release tag and project version differ.

Fixes #93

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@twalen
twalen merged commit fafcc49 into master Oct 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release v2.3.2 to PyPI

1 participant