You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As explained on Slack, I think git describe is (maybe) not a good way to detect the "proper" tag. We should first use git tag --points-at to detect the legitimate latest tag if a commit has multi tags (sort by -version:creatordate). If none is found/valid then we can use git describe --tags --abbrev=0.
@caarlos0
Refs. goreleaser/goreleaser-action#238 goreleaser/goreleaser-action#239
As explained on Slack, I think
git describe
is (maybe) not a good way to detect the "proper" tag. We should first use git tag --points-at to detect the legitimate latest tag if a commit has multi tags (sort by-version:creatordate
). If none is found/valid then we can usegit describe --tags --abbrev=0
.You can find an implementation in our GitHub Action.
The text was updated successfully, but these errors were encountered: