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)
• .github/workflows/build.yaml (github-actions)
• go.mod (gomod)
• deploy/charts/example-approver-policy-plugin/values.yaml (helm-values)
• deploy/charts/example-approver-policy-plugin/Chart.yaml (helmv3)

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.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• 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 5 Pull Requests:

Update actions/checkout action to v5.0.1

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to 93cb6efe18208431cddfb8368fd83d5badbf9bfd

Update module k8s.io/apimachinery to v0.34.2

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

Update actions/setup-go action to v6.1.0

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

Update Helm release cert-manager-approver-policy to v0.22.2

• Schedule: ["at any time"]
• Branch name: renovate/cert-manager-approver-policy-0.x
• Merge into: main
• Upgrade cert-manager-approver-policy to 69e218ef72b52a8bedc78bd1fc4f60f773c23983cbc75484314acfbccf1b717c

Update actions/checkout action to v6

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

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

---

Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

• Failed to look up docker package my-org/cert-manager-example-approver-policy-plugin

Files affected: deploy/charts/example-approver-policy-plugin/values.yaml

---

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

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign maelvls for approval. For more information see the Code Review Process.

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

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

[cert-manager-prow]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• a03743d Add renovate.json

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-sigs/prow repository. I understand the commands that are listed here.