fix: retrigger release after semantic-release tag conflict on v2.0.1 - #16
Merged
Conversation
Previous semantic-release run created tag v2.0.1 and published to PyPI successfully but failed on a re-run due to an existing tag conflict. This commit triggers a clean v2.0.2 patch release.
haimsch
approved these changes
Aug 19, 2026
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
2 participants
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.
Previous semantic-release run created tag
v2.0.1and published to PyPI successfully, but failed on a subsequent re-run due to the existing tag.This empty
fix:commit triggers a cleanv2.0.2patch release.