In the Kubernetes ecosystem, I frequently run into a problem where I want
to use some custom resource but its API package is in the same module as
its controller (and loads of other crap) that have a massive dependency
chain (often broken and "fixed" with replace directives). In several
instanc
On Wednesday, February 24, 2021 at 7:42:24 PM UTC-8 Bryan C. Mills wrote:
> That said, that kind of coordinated release is *really* unpleasant, so
> this is one of the motivating problems for https://golang.org/issue/36460
> (which I've been actively working on since basically the start of 2020)
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 C
s/transient/transitive/
--
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:
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 thei
