Creating a release based on a commit that has multiple tags failed half-way with 'already_exists'

[miparnisari]

Hi everyone!

On this repo: https://github.com/authzed/spicedb, we have a commit that points to two different tags: authzed/spicedb@afd982c: [v1.47.0, v1.46.2]

When I pushed the tag for v1.47.0, it seems that Goreleaser didn't "see" it

  • getting and validating git state
    • git state                                      commit=afd982cf7b0997eaa5ee60016e820b5d789d1c0a branch=HEAD current_tag=v1.46.2 previous_tag=v1.46.1 dirty=false

and hence it tried to make a release off a tag that already had been released, which failed towards the end: https://github.com/authzed/spicedb/actions/runs/18853766449/job/53796381537.

This had the undesirable side-effect of rewriting existing images for v1.46.2, which means that people using old images can no longer download them (because the checksum changed). Refer this.

[johnstcn]

Seen here also: https://github.com/coder/terraform-provider-coder/actions/runs/19097548032/job/54561366988

In the above case, it detected current_tag=v2.13.0-pre0 despite the workflow having checked out refs/tags/v2.13.0.

[caarlos0]

it is using the default git tag ordering (refname), you can change that though: https://goreleaser.com/customization/git/

that said, this is working as intended.