Release prebuilt binaries

[Utsav2]

We'd really like to deploy go-langserver for an internal code search tool, but right now, we'd have to check in all the code for go-langserver and its dependencies and build it before we can use it. If possible, we'd really like to have prebuilt binaries so that we can directly use them.

It would be of great help if you could cut a new release, and include the built binary as part of it. That way, our internal build system can automatically pick it up. Thanks!

Here's an example of an open source project that includes "assets" https://github.com/bazelbuild/bazel/releases.

[tylerFowler]

This would also help out with my Atom IDE package, simply using go get is suboptimal as I can't easily check out a specific tag and build from that. Having a stable URL for different builds of each version would help insulate users from getting incompatible versions.

[nicksnyder]

I just setup goreleaser for another repo and it works great

example: https://github.com/sourcegraph/yj/commit/21a756b4e74f0c1fabb7910b4eae04609fc86d1b https://github.com/sourcegraph/yj/releases/tag/v1.0.0

[keegancsmith]

goreleaser looks cool and easy to setup. Lets do it, happy to accept a PR that integrates it.

[emidoots]

+1 for goreleaser, looks neat! Of course it's also very easy to roll our own as I did in src-cli using gox: https://github.com/sourcegraph/src-cli/blob/master/.travis.yml I think it should be easy to copy the same travis yaml here and generate a new travis API key.

[nicksnyder]

A CI solution would be ideal for this project, but I didn’t bother with that in my example because those are small tools.