I’m trying to get rid of a transient dependency on 
k8s.io/[email protected]+incompatible and I’ve tracked it down to the 
co-dependency of Thanos and Cortex... Presumably, there isn't a dependency 
cycle in their packages, but there is in their modules (at different 
versions). The two update their versions of each other independently so 
there’s a trampoline leading all the way back to the k8s.io/client-go problem 
a year ago:

github.com/thanos-io/[email protected] 
github.com/cortexproject/[email protected]
github.com/cortexproject/[email protected] 
github.com/thanos-io/[email protected]
github.com/thanos-io/[email protected] 
github.com/cortexproject/[email protected]
github.com/cortexproject/[email protected] 
github.com/thanos-io/[email protected]
github.com/thanos-io/[email protected] 
github.com/cortexproject/[email protected]
github.com/cortexproject/[email protected] 
github.com/thanos-io/[email protected]
github.com/thanos-io/[email protected] 
github.com/cortexproject/[email protected]
github.com/cortexproject/[email protected] 
github.com/thanos-io/[email protected]
github.com/thanos-io/[email protected] 
github.com/cortexproject/[email protected]
github.com/cortexproject/[email protected] 
github.com/thanos-io/[email protected]
github.com/cortexproject/[email protected] 
github.com/prometheus/[email protected]
github.com/prometheus/[email protected] 
github.com/prometheus/[email protected]
github.com/prometheus/[email protected] 
k8s.io/[email protected]+incompatible

My initial thought was try to work with Thanos and Cortex to either (a) 
detangle their modules or (b) coordinate releases to start a new history 
for their trampoline, but now I'm wondering if this is something that 
should be addressed in the go tool. Perhaps the module "cycle" should be 
detected and newer versions of modules in the cycle should block older 
versions from being traversed?

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/87d41930-8b03-467a-ac49-78010de7056en%40googlegroups.com.

Reply via email to