Do not create duplicate draft release in GitHub

[qsliu2017]

Is your feature request related to a problem? Please describe.

Our release workflow is like this:

1. Create a vx.y.z branch, then GitHub Actions create a draft release with the name RELEASE vx.y.z
2. In the next couple of day, we cherry-pick some bug-fix commit to the release branch as well as fill the content of the release note

The question is a new commit to the release branch will trigger goreleaser again, and create another draft release note (instead of appending to the existing one).

Seems like goreleaser only treat releases with the same tag as the same releases. While the draft release will be assigned a random tag like untagged-1070a2429328d38d3638.

goreleaser/internal/client/github.go

Lines 224 to 230 in f8e5bda

	release, _, err = c.client.Repositories.GetReleaseByTag(
	ctx,
	ctx.Config.Release.GitHub.Owner,
	ctx.Config.Release.GitHub.Name,
	data.GetTagName(),
	)
	if err != nil {

Describe the solution you'd like

Consider treating draft releases with the same name as the same release

Describe alternatives you've considered

N/A

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

No response

[caarlos0]

refs #3073 #3072 cc27fba

[qsliu2017]

@caarlos0 Could you explain why #3073 fail? thanks.

[caarlos0]

yes, if you run goreleaser multiple times, reusing the same release (i.e. the draft), it'll fail to upload the artifacts because they already exist.

so, in order to reuse, you'll probably need to delete the release artifacts first.

[github-actions]

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.