You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed a binary via go get at an older version than the corresponding lib that I was using. This silently removed a seemingly unrelated dependency, cause a subsequent build of my package to fail because the dependency was automatically re-added, but at the latest version.
module myproject
go 1.14
require (
github.com/some/lib v1.1.0 // depends on github.com/other/lib v1.5.0
github.com/other/lib v1.5.0
...
)
Installing an old binary via go get github.com/other/lib/cmd/binary v1.4.0 can remove the dependency on github.com/some/lib if there is no old version of some/lib that matches the v1.4.0 target.
The problem is that this removal is completely silent.
A subsequent build of myproject will automatically re-add the dependency, but at the latest version.
What did you expect to see?
I'd like a clear message indicating if seemingly unrelated dependencies are removed because no acceptable combination of versions was found.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?What did you do?
I installed a binary via
go get
at an older version than the corresponding lib that I was using. This silently removed a seemingly unrelated dependency, cause a subsequent build of my package to fail because the dependency was automatically re-added, but at the latest version.Installing an old binary via
go get github.com/other/lib/cmd/binary v1.4.0
can remove the dependency ongithub.com/some/lib
if there is no old version ofsome/lib
that matches thev1.4.0
target.The problem is that this removal is completely silent.
A subsequent build of
myproject
will automatically re-add the dependency, but at the latest version.What did you expect to see?
I'd like a clear message indicating if seemingly unrelated dependencies are removed because no acceptable combination of versions was found.
The text was updated successfully, but these errors were encountered: