Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: for v0 dependencies, consider changing 'go get -u[=patch]' behavior, or otherwise improve related behavior #28396
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
This issue is more about the general concern, but at this point I have seen multiple problems with modules where someone followed older instructions saying
One concrete example was that if you opted in to modules, and then followed the installation instructions for
I first saw this example with v1.15.21 of aws-sdk-go, which did have a
That particular instance of this problem was diagnosed and then worked around (by not using
We certainly should not change
As you note, the possibility of breaking changes with
At any rate, it's not at all clear to me why the folks maintaining
referenced this issue
Nov 16, 2018
Since the library used a vendor directory the usage of the update flag did not impact users getting the library using Go 1.10 and earlier since the dependencies were vendored. This behavior changed when a module file (go.mod) is defined with Go 1.11's module support enabled. The update flag does get the latest dependencies, ignoring the content of the vendor folder. I've updated the library's instructions.
Also @thepudds would you mind opening up a GitHub issue with