-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: 'go get' should show requirement chains for inconsistent versions #35167
Comments
The
In this case, it happens because the module transitively requires a newer version of itself. Is |
I think we should probably show a better error message here the full chain of requirements. gorelease should also warn about this condition. |
Ah! So the solution is to tag |
Yes, just so it sorts after If there's anything after a |
That worked - thank you!
Do you want to close this issue, or use it track "better error message"? |
Let's track it as a diagnostic issue. A better message would be:
|
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?
What did you expect to see?
It works.
What did you see instead?
It does not work. I assume it's because there's a path from v1.0.1-beta to v1.0.1 (see below), but not sure why that's a problem.
The text was updated successfully, but these errors were encountered: