goreleaser: release fails

[nodece]

Describe the bug

The following is my log:

 ⨯ release failed after 0.08s error=git tag v2.2.2 was not made against commit 04c96314107df0803aa1e7ffaf3cd4784911a88c

It looks a git issue.

track https://github.com/goreleaser/goreleaser/blob/master/internal/git/git.go#L31 and https://github.com/goreleaser/goreleaser/blob/master/internal/pipe/git/git.go#L108, I found error is exit status 128 .

What did validate do?

To Reproduce

Steps to reproduce the behavior:

project_name: casbin

release:
  github:
    owner: casbin
    name: casbin

  disable: true

  name_template: "Casbin {{.Version}}"

changelog:
  sort: asc
  filters:
    exclude:
      - '^docs:'
      - '^test:'
      - Merge pull request
      - Merge branch

Make sure your config file is valid by running
goreleaser check -f path-to-config-file.

Expected behavior

It is working.

Environment (please complete the following information):

• OS: mac
• OS version: 10.14.6
• GoReleaser Version [0.131.1]
• GitLab version (if using a private hosted one)
• Git: git version 2.21.1 (Apple Git-122.3)

Additional context

[caarlos0]

you tagged and commit after that, so your current commit is 04c96314107df0803aa1e7ffaf3cd4784911a88c but that is not the commit at which the tag was made.

you either need to checkout to the tag and run goreleaser, or create a new tag.

What did validate do?

this step is to ensure that the binaries built for a given tag are actually built from the correct commit.

[nodece]

I need the goreleaser can detect next tag and create it via commit log.
Looks like https://github.com/semantic-release/semantic-release.

I don't know what to do.

[caarlos0]

goreleaser does not do that.

tag needs to be there beforehand.

[nodece]

Thanks for your timely response.

[nodece]

I know what to do.