-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependabot downgraded github.com/cert-manager/cert-manager v1.8.0 => v0.7.2 as a result of upgrading k8s.io/component-base #71
Comments
Hmm, 0.7.2 is the last version that exists before we started using go modules. There is possibly some transitive dependency clash. We really need to split the cert-manager API from the controllers as importing cert-manager in projects that also use k8s.io modules causes these weird issues. |
Looks like dependabot/dependabot-core#4536 |
It seems to downgrade cert-manager as a side-effect of upgrading golang.org/x/sys (for example), $ git reset --hard origin/main
HEAD is now at 06dd31d Merge pull request #54 from wallrj/use-dependabot
# Go 1.18 downgrades cert-manager
$ go1.18.3 get -u golang.org/x/sys
go: downgraded github.com/cert-manager/cert-manager v1.8.0 => v0.7.2
go: upgraded golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e => v0.0.0-20220608164250-635b8c9b7f68
$ git reset --hard origin/main
...
# Go 1.17 downgrades cert-manager
$ go1.17.2 get -u golang.org/x/sys
go get: downgraded github.com/cert-manager/cert-manager v1.8.0 => v0.7.2
go get: upgraded golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e => v0.0.0-20220608164250-635b8c9b7f68
$ git reset --hard origin/main
...
# Go 1.16 does not
$ go1.16.1 get -u golang.org/x/sys
go get: upgraded github.com/Microsoft/go-winio v0.5.0 => v0.5.1
go get: upgraded github.com/spf13/viper v1.8.1 => v1.10.0
go get: upgraded golang.org/x/sys v0.0.0-20211216021012-1d35b9e2eb4e => v0.0.0-20220608164250-635b8c9b7f68 |
Creating a separate |
We enabled dependabot and now it is creating PRs with package upgrades, but strangely, it seems also to be downgrading cert-manager to v0.7.2 E.g.
I get the same result when I manually update that dependency:
The text was updated successfully, but these errors were encountered: