New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: get of @latest does not return latest version #42451
Comments
Is this issue consistently reproducible, or did it resolve? If it is consistent, perhaps try rebuilding |
It definitely seems somewhat random. I will happily try a later version of What would be useful from my perspective would be to clarify how the proxy in certain circumstances:
|
Maybe, although it could also be a bug somewhere in the logic that prunes retracted versions, or something in |
I've just commented over at #42449 (comment) with some further context. I suspect these issues might end up being one and the same cause? |
Closing this in favour of #42449, because it appears to be an artefact of proxy caching (and my incorrect assumption). |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I'm not totally clear this is a
cmd/go
problem; it feels more like a proxy issue. But like #42449 I stumbled across it whilst playing with module retractions.Here is the timestamp sequence of events:
What did you expect to see?
The
go get
should have resulted inv0.4.0
What did you see instead?
v0.3.0
cc @jayconrod @katiehockman @heschik
The text was updated successfully, but these errors were encountered: