update dependencies#86
Conversation
Signed-off-by: emirot <emirot.nolan@gmail.com>
kaovilai
left a comment
There was a problem hiding this comment.
velero-io/velero#9778 is bumping k8s to 1.36 maybe wait for that?
If I understand correctly we will also need to wait for a release right? How long it takes usually? @kaovilai |
|
This is not a release/. So I don't think we need to wait for release, for example, updates here. Just suggesting that perhaps waiting a little bit will avoid having to have two pull requests, but if you need this now, we can just merge it this way. |
|
The main branch will be cut to a release/ at 1.19, and I don’t think that will be a blocker since it’s a few months away. |
@kaovilai thanks for the explanation, whatever makes the more sense, I am just playing with a plugin and thought about updating upstream, but I don't know how those version really matters regarding compatibility with the plugin. And also why dependabot did not? |
|
I believe we want to try to keep things in sync with the other repo. I don't think Dependabot had been set up in a way that keeps all repos in sync in regards to Kubernetes dependencies. |
What
Update dependencies