fix: release pipeline committing to wrong branch#1577
Merged
lkstrp merged 4 commits intoPyPSA:masterfrom Feb 23, 2026
Merged
Conversation
lkstrp
force-pushed
the
fix-release-pipeline
branch
from
458a8ef to
286bfb4
Compare
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.
Changes proposed in this Pull Request
Release
v1.1.1needs to be yanked since it was released from the wrong branch. That could happen since the release preparation step detected the wrong branch when other branches had merged the master already, causing v1.1.1 to be built fromfeat/link-delay.--containsreturns all branches that have the commit anywhere in their history, andhead -n 1picked the first one alphabetically, which doesn't always need to resolve to the master if the was already merged back in between.git branch --points-atwhich only matches branches whose tip is the tagged commit, which fixes the issue.