Closed debovema closed 4 years ago
So this just add binaries with the releases, right ?Are there any other reasons for having this?
Yes and it can also creates nice changelogs and release notes according to configuration.
It's very straightforward for releaser as it is only a tag to create and push.
For end users, it's easier to download a prebuilt binary sometimes. go get
always pull the latest (unstable?) version and building a specific version from source implies to git clone, git checkout the right tag (after finding its name) and go install (pretty complicated for just the CLI).
While the 0.9.1 is in RC, why not enabling Go Releaser to build binaries and put them in GitHub releases page ? Based on the branch of this PR I released a fake version on my repository simply by creating and pushing the v0.9.99 tag. Before that a GITHUB_TOKEN environment variable with a GitHub token (with
write:packages
role) must be added in Travis CI.