infra: merge v1.7.7 release commits into main#196
Merged
Conversation
The v1.7.7 tag points to commit 6b17614 which was created on a release branch and never merged back to main. As a result, main's ancestry only contains v1.7.6, so the release pipeline keeps recomputing the next release as v1.7.7 and failing when it tries to push the already-existing tag. Merging v1.7.7 into main makes the tag reachable from main so the release bot will compute the next version from v1.7.7 going forward.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #196 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 34 34
Lines 1528 1528
Branches 200 200
=========================================
Hits 1528 1528 ☔ View full report in Codecov by Harness. 🚀 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.
The
v1.7.7tag (pushed 2026-06-10) points to commit6b17614('infra: update pypi build step (#193)'), which was created on a release branch and never merged back tomain.This PR merges the
v1.7.7tag intomainwith--no-ff. The merge produces a merge commit with parents48cd779(current main) and6b17614(v1.7.7 tip), making the tag reachable frommain. No files are changed by the merge — thepublish-to-pypi.ymlchanges from #193 had already been re-applied to main via later commits, so this is purely an ancestry fix.After this lands, the next release pipeline run will see
v1.7.7as the latest reachable tag and bump correctly from there.