-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: go.mod should codify dependencies in multi-module mode before tagging new module #32344
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
Comments
Hi @jadekler Maybe this is an incarnation of #27063? Does |
What do you mean by “codify”? This is most definitely another instance of #27063:
|
Duplicate of #27063 |
Stick into the go.mod.
Does this edit the go.mod? |
It does if there are no errors. |
For posterity, from https://code-review.googlesource.com/c/gocloud/+/41530:
|
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?
(the subdir is https://github.com/googleapis/google-cloud-go/tree/master/logging)
What did you expect to see?
A go.mod with all the
subdir
dependencies codified.What did you see instead?
(actually, using real example, the module name is
cloud.google.com/go/logging
)Why does
go mod tidy
not codify all the newly-carved-out module's dependencies? Similarly,go mod graph
returns nothing:I assume that once I publish a logging/v0.0.1,
go mod tidy
will magically begin working as expected...?The text was updated successfully, but these errors were encountered: