Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: firstname.lastname@example.org+incompatible currently allows Semantic Import Versioning to be optional #32695
This is a spinout from "Factor 2" from #31543 ("cmd/go: creating v2+ modules has lower success rate than it could").
Compared to Go 1.11 and 1.12, current tip / 1.13 might have increased the modes of interaction that work with v2+ modules that have not adopted Semantic Import Versioning.
What version of Go are you using (
Hmm, this is unfortunate. In direct mode, it seems we correctly don't list these versions:
However, the proxy knows about them.
And in your example, the Go command validation doesn't catch the problem with these versions, even with
Patching in https://golang.org/cl/181881, it looks like a go.mod with a version like this will break the build in direct mode, since it's now validated.
We should figure out how many modules have invalid requirements like this.
I think another example of this is
EDIT: On a second look, setting
That first result is the intended behavior; the second is this bug.