I’m trying to get rid of a transient dependency on k8s.io/client-go@v12.0.0+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/thanos@v0.18.0 github.com/cortexproject/cortex@v1.5.1-0.20201111110551-ba512881b076 github.com/cortexproject/cortex@v1.5.1-0.20201111110551-ba512881b076 github.com/thanos-io/thanos@v0.13.1-0.20201030101306-47f9a225cc52 github.com/thanos-io/thanos@v0.13.1-0.20201030101306-47f9a225cc52 github.com/cortexproject/cortex@v1.4.1-0.20201030080541-83ad6df2abea github.com/cortexproject/cortex@v1.4.1-0.20201030080541-83ad6df2abea github.com/thanos-io/thanos@v0.13.1-0.20201019130456-f41940581d9a github.com/thanos-io/thanos@v0.13.1-0.20201019130456-f41940581d9a github.com/cortexproject/cortex@v1.3.1-0.20200923145333-8587ea61fe17 github.com/cortexproject/cortex@v1.3.1-0.20200923145333-8587ea61fe17 github.com/thanos-io/thanos@v0.13.1-0.20200807203500-9b578afb4763 github.com/thanos-io/thanos@v0.13.1-0.20200807203500-9b578afb4763 github.com/cortexproject/cortex@v1.2.1-0.20200805064754-d8edc95e2c91 github.com/cortexproject/cortex@v1.2.1-0.20200805064754-d8edc95e2c91 github.com/thanos-io/thanos@v0.13.1-0.20200731083140-69b87607decf github.com/thanos-io/thanos@v0.13.1-0.20200731083140-69b87607decf github.com/cortexproject/cortex@v0.6.1-0.20200228110116-92ab6cbe0995 github.com/cortexproject/cortex@v0.6.1-0.20200228110116-92ab6cbe0995 github.com/thanos-io/thanos@v0.8.1-0.20200109203923-552ffa4c1a0d github.com/cortexproject/cortex@v0.6.1-0.20200228110116-92ab6cbe0995 github.com/prometheus/alertmanager@v0.19.0 github.com/prometheus/alertmanager@v0.19.0 github.com/prometheus/prometheus@v0.0.0-20190818123050-43acd0e2e93f github.com/prometheus/prometheus@v0.0.0-20190818123050-43acd0e2e93f k8s.io/client-go@v12.0.0+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 golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/87d41930-8b03-467a-ac49-78010de7056en%40googlegroups.com.
