ci: fix release baseline (select by tag name, not reachability) [bump:patch]#15
Merged
Merged
Conversation
…atch] The --merged HEAD filter was wrong: vendor publishes each release by committing the lock + pushing ONLY the tag (master is protected), so release tags point at detached commits that are never on any branch's ancestry. On master --merged saw only v0.1, collapsing the baseline and cutting a bogus v0.2.0. Select the baseline by tag NAME instead: a release/vX.Y branch restricts to its X.Y line (vX.Y, vX.Y.Z), master/other refs use all clean tags globally. This restores correct mainline bumping and keeps back-patch isolation, both compatible with detached release tags. Flavor/suffixed tags stay excluded. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Regression
The
--merged HEADbaseline filter (added for back-patch scoping) is incompatible with howvendortags releases: it commits the lock and pushes only the tag (master is protected), so every release tag points to a detached commit that's on no branch's ancestry.Result on
master:git tag --merged HEADsaw onlyv0.1→ baseline collapsed to0.1→ it cut a bogusv0.2.0.Fix
Select the baseline by tag name, not git reachability:
release/vX.Y(orrelease/vX.Y.Z) → restrict to thatX.Yline (vX.Y,vX.Y.Z)master/ any other ref → all clean tags globally (highest bysort -V)Keeps back-patch isolation, restores correct mainline bumping, and works with detached tags. Flavor/suffixed tags remain excluded. Verified against representative tag sets (master, release lines, flavor +
toolchainexclusions).Note
Touches
vendor.yml→ merging triggers a release. After the tag cleanup (baseline back tov0.5), this merge cuts the correctedv0.6.0.