Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• Dockerfile (dockerfile)
• go.mod (gomod)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 9 Pull Requests:

Update golang Docker tag to v1.24.3

• Schedule: ["at any time"]
• Branch name: renovate/golang-1.x
• Merge into: master
• Upgrade golang to 1.24.3-bullseye

Update kubernetes packages to v0.33.0

• Schedule: ["at any time"]
• Branch name: renovate/kubernetes-go
• Merge into: master
• Upgrade k8s.io/api to v0.33.0
• Upgrade k8s.io/apimachinery to v0.33.0
• Upgrade k8s.io/client-go to v0.33.0

Update module github.com/IBM/controller-filtered-cache to v0.3.6

• Schedule: ["at any time"]
• Branch name: renovate/github.com-ibm-controller-filtered-cache-0.x
• Merge into: master
• Upgrade github.com/IBM/controller-filtered-cache to v0.3.6

Update module github.com/onsi/ginkgo to v1.16.5

• Schedule: ["at any time"]
• Branch name: renovate/github.com-onsi-ginkgo-1.x
• Merge into: master
• Upgrade github.com/onsi/ginkgo to v1.16.5

Update module github.com/onsi/gomega to v1.37.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-onsi-gomega-1.x
• Merge into: master
• Upgrade github.com/onsi/gomega to v1.37.0

Update module github.com/operator-framework/operator-lifecycle-manager to v0.31.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-operator-framework-operator-lifecycle-manager-0.x
• Merge into: master
• Upgrade github.com/operator-framework/operator-lifecycle-manager to 8b47a957340e5559e250f17f63003c1a60d9754f

Update module sigs.k8s.io/controller-runtime to v0.20.4

• Schedule: ["at any time"]
• Branch name: renovate/sigs.k8s.io-controller-runtime-0.x
• Merge into: master
• Upgrade sigs.k8s.io/controller-runtime to v0.20.4

Update module github.com/onsi/ginkgo to v2

• Schedule: ["at any time"]
• Branch name: renovate/github.com-onsi-ginkgo-2.x
• Merge into: master
• Upgrade github.com/onsi/ginkgo to v2.23.4

Update module k8s.io/klog to v2

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-klog-2.x
• Merge into: master
• Upgrade k8s.io/klog to v2.130.1

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR was generated by Mend Renovate. View the repository job log.

[ibm-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: renovate[bot]
Once this PR has been reviewed and has the lgtm label, please assign daniel-fan for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ibm-ci-bot]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a IBM member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.