How to use release->target_commitish field

[blacktop]

This feature seems like something I'd love to use because I often make mistakes and have goreleaser releases fail and I have to remove the releaes/tag and redo it and it creates a lot of noise to people that watch my repo or follow me but I just tried it and got this:

release:
  draft: true
  replace_existing_draft: true
  target_commitish: "{{ .Commit }}"

❯ make release-commitish 
 > Creating Release v3.1.200
git tag -a v3.1.200 -m "Release v3.1.200"
  • starting release...
  • loading config file                              file=.goreleaser.yml
  • loading environment variables
  • getting and validating git state
    • building...                                    commit=36b0df21d2ffb7f05704e085673f2a46855444d1 latest tag=v3.1.200
  • parsing tag
  • setting defaults
  • running before hooks
    • running                                        hook=go mod tidy
    • running                                        hook=go generate ./...
    • running                                        hook=./hack/make/completions
    • running                                        hook=./hack/make/manpages
    • running                                        hook=./hack/make/json_mini
    • took: 20s
  • checking distribution directory
  • loading go mod information
  • build prerequisites
  • writing effective config file
    • writing                                        config=dist/config.yaml
  • building binaries
    • building                                       binary=dist/linux_amd64_build_linux_amd64_v1/ipsw
    • building                                       binary=dist/windows_amd64_build_windows_amd64_v1/ipsw.exe
    • building                                       binary=dist/darwin_ios_build_ios_arm64/ipsw
    • building                                       binary=dist/darwin_arm64_extras_build_darwin_arm64/ipsw
    • building                                       binary=dist/linux_arm64_build_linux_arm64/ipsw
    • building                                       binary=dist/darwin_build_darwin_amd64_v1/ipsw
    • building                                       binary=dist/windows_arm64_build_windows_arm64/ipsw.exe
    • building                                       binary=dist/darwin_build_darwin_arm64/ipsw
    • building                                       binary=dist/darwin_amd64_extras_build_darwin_amd64_v1/ipsw
    • running hook                                   hook=./hack/make/delete-all-rpaths /Users/blacktop/Developer/Github/blacktop/ipsw/dist/darwin_amd64_extras_build_darwin_amd64_v1/ipsw
    • running hook                                   hook=./hack/make/codesign /Users/blacktop/Developer/Github/blacktop/ipsw/dist/darwin_ios_build_ios_arm64/ipsw
    • running hook                                   hook=./hack/make/delete-all-rpaths /Users/blacktop/Developer/Github/blacktop/ipsw/dist/darwin_arm64_extras_build_darwin_arm64/ipsw
    • took: 3s
  • universal binaries
    • creating from 2 binaries                       binary=dist/darwin_build_darwin_all/ipsw id=darwin_build
  • generating changelog
    • took: 3s
  ⨯ release failed after 25s                 error=GET https://api.github.com/repos/blacktop/ipsw/compare/v3.1.199...v3.1.200?per_page=100: 404 Not Found []
make: *** [release-commitish] Error 1

[caarlos0]

that field only tells github to create the tag with the name in the remote once it creates the release.

that won't work with the github changelog config, because the tag is not there yet.

it'll also not remove previously existing tags with the same name.

[blacktop]

Aww 😞, thanks for the answer and that makes sense, but perhaps there could be a config validation step that detects the existence of both configs being set and errors out before running?

[caarlos0]

you can set target commitish, and the tag might still be there... so I can't reliably do that...

I guess we could fallback to plain git changelog if the others fail though