cmd/go: go get of nested module picks version from outer module #61237
Labels
FrozenDueToAge
GoCommand
cmd/go
modules
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
This is a continuation of #56974, which was closed due to being stale and I cannot reopen.
What is the URL of the page with the issue?
https://pkg.go.dev/github.com/twmb/franz-go/pkg/kadm@v1.6.0
Screenshot
What did you do?
I have a repo, github.com/twmb/franz-go with a module at the top-level repo root and other modules at subdirectories. Whenever I release the repo root (push a tag), I can
go get -u
the new version of the project within seconds. When I release a sub-module, it takes more time -- and if I release the main module quickly followed by a submodule, it takes tens of minutes (I'm not sure when / if the cache will purge).Repo structure:
I've managed tags like this for over a year now, and the wait for submodules has never been this long.
What did you expect to see?
go get github.com/twmb/franz-go/pkg/kadm@v1.6.0
to not fail for 30 minutes.What did you see instead?
for 30 minutes
Now, this is happening again -- a separate submodule is also now at 1.6.0 (coincidentally the same as this original issue).
This is happening on v1.20.5.
I released a new module, github.com/twmb/franz-go/pkg/kmsg@v1.6.0.
The Go command does not issue any http requests. I suspect it's because I have old franz-go versions in my mod cache:
So go sees franz-go@v1.6.0 exists, but because kmsg is a separate module, the pkg is not in that top-level module:
I suspect this is causing the failure we see.
The text was updated successfully, but these errors were encountered: