To summarize the concrete issue: An old version of Prometheus pulled in k8s.io/client-go@v12.0.0+incompatible . An old version of Alertmanager pulled in that version of Prometheus. An old version of Cortex pulled in that version of Alertmanager. An old version of Thanos pulled in that version of Cortex A newer version of Cortex pulled in that version of Thanos A newer version of Thanos pulled in that version of Cortex ... A newer version of Cortex pulled in that version of Thanos A newer version of Thanos pulled in that version of Cortex A recent version of Cortex pulled in that version of Thanos A recent version of Thanos pulled in that version of Cortex
Newer versions of Prometheus have moved to k8s.io/client-go@v0.20.2. Newer versions of Alertmanager don't depend on Prometheus. Newer versions of Cortex have moved to newer versions of Alertmanager. Newer versions of Thanos have moved to newer versions of Cortex. Newer versions of Cortex have moved to newer versions of Thanos. Because the k8s release tagging conventions predate go modules, go treats k8s.io/client-go@v12.0.0+incompatible as newer than k8s.io/client-go@v0.20.2, and the cycle between Thanos and Cortex keeps their oldest history together alive in the dependency graph, if you depend on Thanos then you get stuck with k8s.io/client-go@v12.0.0+incompatible and must use replace directives. -- 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/f56e3d1c-620c-4209-9c19-dd0be0c9b16bn%40googlegroups.com.
