get/latest could be better about goreleaser

[jorinvo]

Also see #93 (comment), we should not only offer the latest version. Should give users the choice to keep using one stable version.

Personally, though, I prefer installing GoReleaser via go get since Go is always available in the context you are using GoReleaser...

[caarlos0]

@medhoover yeah, but that could take a while...

[caarlos0]

I guess we can close this one...

[caarlos0]

@jorinvo that makes sense, maybe we should update docs then.

Using go get indeed makes more sense...

[caarlos0]

About getting an specific version, I guess gopkg.in kind of solves that, no?

[jorinvo]

@caarlos0 Nice! I didn't know about gopkg.in before :)
Should we reference it as the goto way of using GoReleaser?
Or should we stick with the latest option as default? As soon as we are stable on 1.0 I think we should commit to a stable API in any case...

[caarlos0]

@jorinvo I think that for now we can use go get or leave as is.

As soon as v1 is released, we can change docs to use http://gopkg.in/goreleaser/goreleaser.v1, that way people using go get will still get the latest version, but can change it to v1 if needed.

[mogharsallah]

About the version link, a solution for the version issue is currently being prepared.
The Saga of Go Dependency Management

[github-actions]

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.