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: confusing go mod experience #49416
Comments
This might be caused by the fact that the two markdown libraries use But any way, all the builds should succeed. |
output of |
Generally, I don't post the
|
In short. the
|
At the first
At the second
At the third
The operation of |
FWIW, I agree that the behavior here is a bit confusing but I don't see a better alternative. (It would be arguably even more confusing if |
@go101, can you give a bit more detail about why you expected the third (I've also sent https://gitlab.com/golang-commonmark/markdown/-/merge_requests/3 upstream to avoid the incompatible upgrade in this case to begin with.) |
|
In this case, |
But I don't know what is the exact version of the indirect dependency module. |
See https://golang.org/doc/modules/version-numbers. You don't have to request the exact version; |
Assume I know it is a
The |
Yes, that's true. We don't in general have a way to downgrade a dependency to the minimum of the versions already required by other dependencies, and I haven't seen a strong use-case for it. (Typically if you had a working build with an earlier set of dependencies you can use It would also be fairly straightforward to build a third-party tool to perform that downgrade using |
I find vacuuming the require lines in the |
I don't think there's anything specific we can do here, but I'll bear this report in mind when we're looking for patterns of workflows and/or documentation to improve. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What did you do?
What did you expect to see?
There are 4
go build
runs, the 3rd one is expected to succeed.What did you see instead?
It fails with many errors.
The text was updated successfully, but these errors were encountered: