chore: trigger release after 0.148.0 tag rebase#1690
Merged
Conversation
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.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ 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 Sentry. 🚀 New features to boost your workflow:
|
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
chorecommit to retrigger python-semantic-release on master after the0.148.0tag was rebased to a master ancestor.Background
When #1688 merged, the
releasejob logged:pyproject.tomlwas at0.147.4. Thefeat:commit since then prompted PSR to propose0.148.0, but a0.148.0git tag already existed — orphaned, from commitb43d039on the abandoned 1.x line that was later reverted via #1674. PyPI's0.148.0is also occupied (unyanked, foreign code, uploaded 2025-10-05).To unblock PSR without reusing a published version:
legacy/0.148.0(still on the remote, pointing atb43d039).0.148.0tag from the remote.0.148.0on master ancestorc96a997(thefeat(core): add use_asyncio kwargcommit — the change that would have been0.148.0in the post-revert line).PSR will now walk back from master HEAD, find
0.148.0atc96a997, see thefeat: drop Python 3.9 supportcommit since then, bump minor →0.149.0, create the tag, andupload_pypiwill publish since0.149.0is free on both git and PyPI.Test plan
releasejob logs a0.149.0release.0.149.0lands on PyPI and thebuild_wheelsmatrix runs to completion.legacy/0.148.0later once the recovery is documented.