Provide binaries and releases

[google]

Provide binaries and releases

[DylanMeeus]

Running into the same issue here :/

[gssbzn]

@DylanMeeus the way we solved this was running go get with GO111MODULE=on, we just had to go thru some hoops on our ci as running go get with GO111MODULE=on in a folder with a go.mod file will add the dependency to the file (this is a known "feature" with no way around it so far) and we did not want that on our ci, hence why I think binaries would help a lot

[DylanMeeus]

Thanks @gssbzn, I'll give that a try!
Luckily nothing urgent though as we don't update our external dependencies all that often. Having release tags would help a great deal in preventing these issues :-)

[RJPercival]

Would a Docker image suffice? There's already a Dockerfile that should always build, and it should be relatively easy to release Docker images.

[gssbzn]

@RJPercival it would be a start for sure, our ci doesn't have the best docker support but we are working on it.
I also have some experience setting up goreleaser if that's an approach some of the contributors are willing to try I'm happy to make a PR but having something like that means the maintainers are happy to at least tag the release

[RJPercival]

They should be happy to tag a release; the v1 milestone is complete so I think it's ready for a v1.0.0 tag. I'm not so sure about goreleaser; they'll have to chime in there.

[gssbzn]

with go1.16 I think this can be closed as in theory now there's an option to not alter the the go.mod file, I still need to test this on our CI env as we are still adding 1.16 support

[Bobgy]

There are releases now and with go1.16+ go install github.com/google/go-licenses@latest, I think these problems are addressed. Please comment if it's still an issue.