🌱 dependabot: remove go modules bumps, bump all actions at once #2856
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Stefan Büringer buringerst@vmware.com
We recently introduce a linter which ensure that our dependencies stay in sync with k/k.
This is important so consumers of CR don't run into compile issues between transitive dependencies of CR & k/k (e.g. if we would use different prometheus versions).
Through this validation we realized that it's basically impossible to bump any dependencies without running out-of-sync in some way with k/k (e.g. even bumping ginkgo leads to a lot of out-of-sync dependencies: #2842 / https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_controller-runtime/2842/pull-controller-runtime-test/1795194368211030016)
This PR: