Skip to content
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

Closed
3 tasks done
yogeshlonkar opened this issue Aug 30, 2022 · 7 comments · Fixed by #3349
Closed
3 tasks done

Changelog in GitHub release no longer has commit links #3348

yogeshlonkar opened this issue Aug 30, 2022 · 7 comments · Fixed by #3349
Assignees
Labels
bug Something isn't working

Comments

@yogeshlonkar
Copy link

yogeshlonkar commented Aug 30, 2022

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 tag

goreleaser version

goreleaser version 1.11.1
commit: c81221016704e3f2dff72b60903f7f5f72c6f640
built at: 2022-08-29T13:25:05Z
built by: goreleaser
goos: linux
goarch: amd64
module version: v1.11.1, checksum: h1:RQsTQSmBqvmpcBCbQ4gSja1g32Z4xWokyOmq/Y0uEDY=

https://goreleaser.com

GoReleaser Check

  • goreleaser check shows no errors

Search

  • I did search for other open and closed issues before opening this.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Additional context

Screenshot releases done through latest version

Screenshot 2022-08-30 at 13 00 43

Screenshot 2022-08-30 at 13 05 08

Old release note content

image

@yogeshlonkar yogeshlonkar added bug Something isn't working triage Issue pending triage by one of the maintainers labels Aug 30, 2022
@caarlos0
Copy link
Member

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:

func commitAbbrevLen(ctx *context.Context) int {

is your repo public? if so, I can investigate more...

@caarlos0
Copy link
Member

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 caarlos0 removed the triage Issue pending triage by one of the maintainers label Aug 30, 2022
@yogeshlonkar
Copy link
Author

@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

@caarlos0
Copy link
Member

@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

@caarlos0
Copy link
Member

check #3349

@yogeshlonkar
Copy link
Author

This should fix it, I'll check with in next version

@github-actions
Copy link
Contributor

github-actions bot commented Dec 5, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants