Goreleaser: V1 Release Planning

[caarlos0]

We still have some issues open for v1:

• #110 (Release to Gitlab) and #15 (upload to bintray): I don't know if we should do this right now, but I'm worried about the API changes it might bring to us. Maybe we should define how our API should look like in those cases and let it be that way in this release, so the next it would be just a matter of adding the implementation?
• #93 (change binary_name to binary): IMO we can just do this. Pre-v1 is for API changes 🗡
• #63 (create website): Is our website good enough? Do we need to change something? If not, this issue might just be closed.
• #56 (improve release changelog): this would be good but also kind of hard to implement - and might get even more complex if we add gitlab support later on. What do you guys think?

[caarlos0]

I believe all these points are solved.

When we are ready, we can merge #147 and release.

[caarlos0]

More stuff entered v1, let's wait a little more.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.