Repository navigation
fix(git): select reachable releases and push only the requested tag - #21
Merged
Merged
Conversation
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
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.
Tag selection could use releases from unrelated branches or lose all tags when Git column output was enabled. Tag pushes could publish additional annotated tags or fail when a branch shared the release tag name.
Select the highest valid tag reachable from HEAD with column output disabled. Push only the fully qualified requested tag ref, explicitly disabling follow-tags.
Closes #13
Closes #14
Closes #15
Closes #16
Validation: all four new regression scenarios failed before the fix and pass now. Real Git repositories and local bare remotes cover tag reachability, column output, push.followTags, and ambiguous ref names.
go test ./...,go vet ./..., and golangci-lint v2.13.0 pass.