Configure Renovate

[gardener-ci-robot]

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.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 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.

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/base.yaml (github-actions)
• .github/workflows/non-release.yaml (github-actions)
• .github/workflows/pr-release-notes-validation.yaml (github-actions)
• .github/workflows/pr-review-timeline.yaml (github-actions)
• .github/workflows/publish-docs.yml (github-actions)
• .github/workflows/release.yaml (github-actions)
• .github/workflows/upgrade-dependencies.yaml (github-actions)
• api/go.mod (gomod)
• client/go.mod (gomod)
• druidctl/go.mod (gomod)
• go.mod (gomod)
• charts/values.yaml (helm-values)

What to Expect

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

Update golang.org/x/exp digest to 746e56f

• Schedule: ["at any time"]
• Branch name: renovate/golang.org-x-exp-digest
• Merge into: master
• Upgrade golang.org/x/exp to 746e56fc9e2f

Update k8s.io/utils digest to 28399d8

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-utils-digest
• Merge into: master
• Upgrade k8s.io/utils to 28399d86e0b5

Update shreyas-s-rao/pr-review-timeline action to v0.2.2

• Schedule: ["at any time"]
• Branch name: renovate/shreyas-s-rao-pr-review-timeline-0.x
• Merge into: master
• Upgrade shreyas-s-rao/pr-review-timeline to v0.2.2

Update dependency go to 1.26

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

Update golang Docker tag to v1.26.2

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

Update module github.com/gardener/etcd-druid/api to v0.36.3

• Schedule: ["at any time"]
• Branch name: renovate/github.com-gardener-etcd-druid-api-0.x
• Merge into: master
• Upgrade github.com/gardener/etcd-druid/api to v0.36.3

Update module github.com/gardener/etcd-druid/client to v0.36.3

• Schedule: ["at any time"]
• Branch name: renovate/github.com-gardener-etcd-druid-client-0.x
• Merge into: master
• Upgrade github.com/gardener/etcd-druid/client to v0.36.3

Update module github.com/Masterminds/semver/v3 to v3.5.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-masterminds-semver-v3-3.x
• Merge into: master
• Upgrade github.com/Masterminds/semver/v3 to v3.5.0

Update module github.com/onsi/ginkgo/v2 to v2.28.3

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

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

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

Update module github.com/spf13/cobra to v1.10.2

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

Update module go.uber.org/zap to v1.28.0

• Schedule: ["at any time"]
• Branch name: renovate/go.uber.org-zap-1.x
• Merge into: master
• Upgrade go.uber.org/zap to v1.28.0

Update module golang.org/x/tools to v0.44.0

• Schedule: ["at any time"]
• Branch name: renovate/golang.org-x-tools-0.x
• Merge into: master
• Upgrade golang.org/x/tools to v0.44.0

Update module k8s.io/api to v0.36.0

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

Update module k8s.io/apiextensions-apiserver to v0.36.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-apiextensions-apiserver-0.x
• Merge into: master
• Upgrade k8s.io/apiextensions-apiserver to v0.36.0

Update module k8s.io/apimachinery to v0.36.0

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

Update module k8s.io/cli-runtime to v0.36.0

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

Update module k8s.io/client-go to v0.36.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-client-go-0.x
• Merge into: master
• Upgrade k8s.io/client-go to v0.36.0

Update module k8s.io/code-generator to v0.36.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-code-generator-0.x
• Merge into: master
• Upgrade k8s.io/code-generator to v0.36.0

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

• 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.24.0

Update module sigs.k8s.io/controller-runtime/tools/setup-envtest to v0.24.0

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

Update module sigs.k8s.io/controller-tools to v0.20.1

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

Update actions/cache action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-cache-5.x
• Merge into: master
• Upgrade actions/cache to v5

Update actions/checkout action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: master
• Upgrade actions/checkout to v6

Update actions/setup-go action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-go-6.x
• Merge into: master
• Upgrade actions/setup-go to v6

Update actions/setup-python action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-python-6.x
• Merge into: master
• Upgrade actions/setup-python to v6

Update actions/upload-artifact action to v7

• Schedule: ["at any time"]
• Branch name: renovate/actions-upload-artifact-7.x
• Merge into: master
• Upgrade actions/upload-artifact to v7

Update module github.com/charmbracelet/lipgloss to v2

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

Update module github.com/charmbracelet/log to v2

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

🚸 PR 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 has been generated by Mend Renovate.

[gardener-robot]

@gardener-ci-robot Thank you for your contribution.

[oliver-goetz]

hey folks 👋

we deployed renovate in our prow cluster and activated it for the repositories where prow is already running 🏡

renovate is an alternative to dependabot which is more flexible in regards of its configuration. You can use it if you like by configuring it using this PR or adding a config file by your own according to the docs.
There are also some hints in ci-infra repository you can check and there is a working configuration too.

If you don't like to use it, just close this PR (but do not rename it) and the 🤖 won't bother you again.

[shreyas-s-rao]

@oliver-goetz thanks. I like that renovate considers even image tags and golang versions for updates, which is quite convenient. But once renovate is enabled, can we still disable it by removing the renovate.json file, if we don't like it, maybe in terms of interactions on the PRs it raises?

[oliver-goetz]

yes, you can deactivate it again by deleting the config file 👍
Btw. I recommend to use a renovate.json5 file as we do in gardener/gardener. Its main advantage is that you are able to create comments there.

[shreyas-s-rao]

Thanks for the suggestion @oliver-goetz . Will take inspiration from the g/g renovate configuration too.

[seshachalam-yv]

/retest

[shreyas-s-rao]

/retest

[gardener-ci-robot]

Branch Conflicted

⚠️ This PR has a merge conflict which Renovate is unable to automatically resolve, so updates to this PR description are now paused. Please resolve the merge conflict manually.