Hi! I came across the failing build from latest PR and I had the same result with a fresh install. I just had some time this WE and I've fixed it by moving from go-dep to the now officially stable Go mod.
Beside fixing the unpredictable behavior of Go-dep, it reduces the size of the repository since vendor folder is not needed anymore and comply to the way Go intend to do package versioning.
Vendoring is managed by Go itself and done locally on the machine. The huge number of files changed comes from removing the vendor folder.
No more command through go dep for managing dependencies, a simple "go build" generate the correct "go.mod" file by looking through the imports. It is possible to specify a version for a dependency by putting "@v1.x" at the end of the go get command.
Hi! I came across the failing build from latest PR and I had the same result with a fresh install. I just had some time this WE and I've fixed it by moving from go-dep to the now officially stable Go mod.
Beside fixing the unpredictable behavior of Go-dep, it reduces the size of the repository since vendor folder is not needed anymore and comply to the way Go intend to do package versioning.
Vendoring is managed by Go itself and done locally on the machine. The huge number of files changed comes from removing the vendor folder.
No more command through go dep for managing dependencies, a simple "go build" generate the correct "go.mod" file by looking through the imports. It is possible to specify a version for a dependency by putting "@v1.x" at the end of the
go getcommand.More info on: Go Modules Wiki