How to know why a specific package version is being set in go.mod?

1.4k views Asked by At

I have a Go repository with a go.mod currently requiring k8s.io/client-go v11.0.1-0.20190409021438-1a26190bd76a+incompatible.

I would like to bump the version of k8s.io/client-go used by my module but, when I change the version to be v0.19.1 (which exists) and then run go mod tidy, the version is set again to k8s.io/client-go v11.0.1-0.20190409021438-1a26190bd76a+incompatible with no explanation.

How to know why a specific package needs to be a specific version? I would like to know which of my requirement needs k8s.io/client-go v11.0.1-0.20190409021438-1a26190bd76a+incompatible.

1

There are 1 answers

0
bcmills On

go mod graph | grep v11.0.1-0.20190409021438-1a26190bd76a should give you a starting point. You can work backwards from there.