Michael Matloob
Michael Matloob
We're closing this in favor of issue https://github.com/golang/go/issues/66175. If we can tell the user to list `go 1.21.0` in their go.mod instead of `go 1.21`, that will help people correct...
After further consideration and discussion with @hyangah @rsc and @samthanawalla we've decided to change the behavior so that if the go.mod lists go 1.X and the current go version is...
I think opening a separate issue for `go mod tidy` adding a third section is a good idea. I think it's a question whether we should preserve more than two...
I think this should work now after https://golang.org/cl/517915. You need to be in the GOROOT/src directory for it to work. It still takes a while to do the initial load...
I think this might be a documentation issue. The words `(what 'go install' would create)` applied to what go install created before the new `go install module@version` functionality was added....
Hm, maybe it's https://go-review.googlesource.com/c/tools/+/190339 ? That's the only recent cgo related change we've made, but I'm not sure how it could be connected.
I think the best option is to do what the TODO suggests and what Bryan suggested in https://github.com/golang/go/issues/63432#issuecomment-1805916772 and parse the ldflags to see if it contains known paths.
@hyangah We expect this to be fixed once 1.21.11 is released with the backported change to download 1.22.0 when 1.22 is listed in `go.mod`, right?