chore: trigger release after 0.148.0 tag rebase - #1690
Merged
bdraco merged 1 commit intoMay 16, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
The orphan 0.148.0 tag (commit b43d039 from the abandoned 1.x pre-revert line) was preserved as `legacy/0.148.0` and the `0.148.0` tag was moved onto master ancestor c96a997. This unblocks python-semantic-release, which was refusing to release because 0.148.0 already existed on the remote. The next PSR run will see 0.148.0 as the latest ancestor and bump to 0.149.0 (minor) for the `feat: drop Python 3.9 support` (#1688) commit since then.
Copy link
Copy Markdown
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## master #1690 +/- ##
=======================================
Coverage 99.76% 99.76%
=======================================
Files 33 33
Lines 3410 3410
Branches 464 464
=======================================
Hits 3402 3402
Misses 5 5
Partials 3 3 ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
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
Empty chore commit to retrigger python-semantic-release on master after the 0.148.0 tag was rebased to a master ancestor.
Background
When #1688 merged, the release job logged:
pyproject.toml was at 0.147.4. The feat: commit since then prompted PSR to propose 0.148.0, but a 0.148.0 git tag already existed — orphaned, from commit b43d039 on the abandoned 1.x line that was later reverted via #1674. PyPI's 0.148.0 is also occupied (unyanked, foreign code, uploaded 2025-10-05).
To unblock PSR without reusing a published version:
PSR will now walk back from master HEAD, find 0.148.0 at c96a997, see the feat: drop Python 3.9 support commit since then, bump minor → 0.149.0, create the tag, and upload_pypi will publish since 0.149.0 is free on both git and PyPI.
Test plan