Feature/goreleaser

[b3n4kh]

Fixes: #38

Adds support for goreleaser to build binary releases and docker images.

See: https://github.com/b3n4kh/mailwhale/releases/tag/v1.0.0 for example release

This might obsolete: #37

[muety]

Pretty cool stuff, thank you! Only added two more minor change requests, if you don't mind.

Closes #28.

[muety]

Oh sorry, one more thing to add. This would actually be quite important for me. Would it be possible to set the title / name of the release to whatever the corresponding Git tag was? So v<tag-here> or sth.

[b3n4kh]

That is the default behavior:

From the goreleaser docs

  # You can change the name of the release.
  # Default is `{{.Tag}}` on OSS and `{{.PrefixedTag}}` on Pro.
  name_template: "{{.ProjectName}}-v{{.Version}} {{.Env.USER}}"

So default is the Tag, but it can be adjusted.

There is also a "header" and "footer" to the release, with a custom text (additionally to the autogenerated changelog)

[muety]

Never mind then! I was just confused by your release being named 1.0.0, while the current version is 0.13.2, but I see you created a 1.0.0 tag, so all good 👍

[b3n4kh]

Yeah, I should have checked version.txt - might be worth considering adding a check in the pipeline to ensure the tag matches the current version.txt.

Offtopic: I personally liked setting the version during build via ldflags - could be discussed in an issue, that would remove the need for the version.txt file during runtime.