What happened?

Using GoReleaser with an existing published Github release make it draft and republish it.
This is painful when using goreleaser for Golang artifact management in addition to another release system like release please or semantic release cause it generates a new github event release published on the repository.

I suspect this behaviour to be related to ef90821#diff-5d19445232b5dbd4efabd983155c6802ae1ef1be4370176f6c30cf766d30ec22R362.

How can we reproduce this?

Manually create a release (a github event release published is triggered)
Run goreleaser (a new github event release published is triggered)

goreleaser version

1.25

GoReleaser Check

• goreleaser check shows no errors

Search

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

Supporter

• I am a sponsor or a Pro customer

Code of Conduct

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

Additional context

No response