New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changelog in GitHub release no longer has commit links #3348
Comments
hmm, weird, for goreleaser release itself it works: https://github.com/goreleaser/goreleaser/releases/tag/v1.11.0 although in goreleaser's case it got the first 7 instead of the first 6 this works by measuring the short commit here: goreleaser/internal/client/github.go Line 67 in c812210
is your repo public? if so, I can investigate more... |
I guess for now we can guard that behind an option, as it is only really useful when cross-releasing (e.g. code in repo a, release in repo b), in which case the longer commit hashes just make it noisier... |
@caarlos0 no the repository is private. In case of goreleaser I think the actual release notes contains 40 character commit hash which GitHub converts to link with 7 characters. I also realise in my repo release notes contain both 6 and 7 character commit hashes, you can see first 2 screenshots |
goreleaser has the first 7, I checked... anyway, I'll guard that behind an option |
check #3349 |
This should fix it, I'll check with in next version |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
After version v1.11.0 changelog in GitHub release no longer has commit links. Till version v1.10.3 commit hash were 40 in length in changelog which GitHub automatically links to commits, since latest versions commit has are 6 in length which GitHub doesn't automatically link to a commit.
How can we reproduce this?
Run
goreleaser release --rm-dist
on GitHub repository with new taggoreleaser version
GoReleaser Check
Search
Code of Conduct
Additional context
Screenshot releases done through latest version
Old release note content
The text was updated successfully, but these errors were encountered: