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-images.yml (github-actions)
• .github/workflows/codeql.yml (github-actions)
• .github/workflows/commitlint.yml (github-actions)
• .github/workflows/helm-publish.yml (github-actions)
• .github/workflows/unit-test.yml (github-actions)
• go.mod (gomod)
• charts/koor-operator/values.yaml (helm-values)
• charts/koor-operator/Chart.yaml (helmv3)
• config/manager/kustomization.yaml (kustomize)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• 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 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.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

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

fix(deps): update k8s.io/utils digest to 9f67429

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-utils-digest
• Merge into: main
• Upgrade k8s.io/utils to 9f6742963106fb1fadd7ec2493d6d6cd689e5318

fix(deps): update module github.com/onsi/gomega to v1.27.7

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

chore(deps): update gcr.io/kubebuilder/kube-rbac-proxy docker tag to v0.14.1

• Schedule: ["at any time"]
• Branch name: renovate/gcr.io-kubebuilder-kube-rbac-proxy-0.x
• Merge into: main
• Upgrade gcr.io/kubebuilder/kube-rbac-proxy to v0.14.1

chore(deps): update golang docker tag to v1.20

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

chore(deps): update helm release cert-manager to v1.12.0

• Schedule: ["at any time"]
• Branch name: renovate/cert-manager-1.x
• Merge into: main
• Upgrade cert-manager to v1.12.0

fix(deps): update kubernetes packages to v0.27.2

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

fix(deps): update module helm.sh/helm/v3 to v3.12.0

• Schedule: ["at any time"]
• Branch name: renovate/helm.sh-helm-v3-3.x
• Merge into: main
• Upgrade helm.sh/helm/v3 to v3.12.0

fix(deps): update module k8s.io/client-go to v11

• Schedule: ["at any time"]
• Branch name: renovate/major-kubernetes-go
• Merge into: main
• Upgrade k8s.io/client-go to v11.0.0+incompatible

🚸 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 has been generated by Mend Renovate. View repository job log here.

[galexrt]

@zalsader I'm not sure if Renovate can alter the "setup" commit unless we manually edit the commit ourselves. What do you think? (Same for the koor-tech/extended-ceph-exporter#29)

Resolves KSD-195

[zalsader]

@zalsader I'm not sure if Renovate can alter the "setup" commit unless we manually edit the commit ourselves. What do you think? (Same for the koor-tech/extended-ceph-exporter#29)

Resolves KSD-195

Yeah, I think we should just forcepush to this branch to change the commit. I wonder though if it will respect commitlint going forward... Can you check the config?

[galexrt]

@zalsader It should respect the commit style automatically, for example see my private project here: https://github.com/galexrt/fivenet/pulls?q=is%3Apr+sort%3Aupdated-desc+is%3Aclosed+author%3Aapp%2Frenovate

It automagically looks at the last X commits to check what style is needed for the actual PRs.

I didn't change any settings during the renovate configuration.

[galexrt]

@zalsader PTAL I have updated the commit message

[zalsader]

It automagically looks at the last X commits to check what style is needed for the actual PRs.

Ah, I know what the issue is then, the first few commits of this repository have a different style than the rest - before we added commitlint. Here's what I had to do for dependabot

[galexrt]

For sake of completeness as I forgot to add the Renovate docs link in my comment about it, see https://docs.renovatebot.com/semantic-commits/

Renovate looks at the last 10 commit messages in the base branch to decide if the repository uses semantic commits. If there are semantic commits, Renovate uses the conventional-commits-detector to decide what convention the commit messages follow.

Merging now.