Handle tagged prerelease release bumps#69
Merged
Conversation
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.
Summary
semver:patchpromotes a tagged prerelease base such as1.0.0rc1to stable1.0.0Release failure addressed
The failed release for #68 stopped in
Resolve release bumpbecausepyproject.tomlis still1.0.0rc1and tagv1.0.0rc1already exists. With this change, a later package-affecting merge carryingsemver:patchcomputes1.0.0instead of trying to recreatev1.0.0rc1.Tests
uv run pytest tests/test_release_workflows.py -quv run pytest -quv run ruff check src tests