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
Resolve conflicts with github.com/google/cel-go update #1055
Comments
I investigated the merge conflicts. The issue is incompatibility between cel-go 0.16.x and cel-go 0.18.x (really 0.17+). cel-go is also a dependency of k8s.io/apiserver, but at version 0.16 Vendor doesn't differentiate between unstable (<1.0) and stable (>1.0) versions for semver, and treats all minors of the same major as being compatible, meaning we can't have two incompatible 0.x dependencies in the same project. When we try to update external-provisioner's We'll have to wait until k8s.io releases library versions with cel-go 0.17+ before we can update the external-provisioner's dependency. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
What happened:
We excluded cel-go from dependabot updates until we can resolve the merge conflicts
#1048
What you expected to happen:
After cel-go is updated, we may need to reenable dependabot with the unignore command.
How to reproduce it:
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: