Skip to content

Configure Renovate #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Configure Renovate #171

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 7, 2025

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)
  • Dockerfile.builder (dockerfile)
  • .github/workflows/release.yml (github-actions)
  • cos-csi-mounter/go.mod (gomod)
  • go.mod (gomod)
  • deploy/ibmCloud/kustomization.yaml (kustomize)
  • deploy/ibmUnmanaged/kustomization.yaml (kustomize)

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 14 Pull Requests:

Replace k8s.gcr.io/sig-storage/csi-node-driver-registrar Docker tag with registry.k8s.io/sig-storage/csi-node-driver-registrar
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.gcr.io-sig-storage-csi-node-driver-registrar-replacement
  • Merge into: main
  • Upgrade k8s.gcr.io/sig-storage/csi-node-driver-registrar to v2.12.0
Replace k8s.gcr.io/sig-storage/csi-provisioner Docker tag with registry.k8s.io/sig-storage/csi-provisioner
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.gcr.io-sig-storage-csi-provisioner-replacement
  • Merge into: main
  • Upgrade k8s.gcr.io/sig-storage/csi-provisioner to v5.1.0
Update golang Docker tag to v1.24.3
  • Schedule: ["at any time"]
  • Branch name: renovate/golang-1.x
  • Merge into: main
  • Upgrade golang to 1.24.3
Update module github.com/onsi/ginkgo/v2 to v2.23.4
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-onsi-ginkgo-v2-2.x
  • Merge into: main
  • Upgrade github.com/onsi/ginkgo/v2 to v2.23.4
Update module google.golang.org/protobuf to v1.36.6
  • Schedule: ["at any time"]
  • Branch name: renovate/google.golang.org-protobuf-1.x
  • Merge into: main
  • Upgrade google.golang.org/protobuf to v1.36.6
Update quay.io/containerstorage/ibm-object-csi-driver Docker tag to v0.1.19
  • Schedule: ["at any time"]
  • Branch name: renovate/quay.io-containerstorage-ibm-object-csi-driver-0.x
  • Merge into: main
  • Upgrade quay.io/containerstorage/ibm-object-csi-driver to v0.1.19
Update registry.access.redhat.com/ubi8/ubi-minimal Docker tag to v8.10-1255
  • Schedule: ["at any time"]
  • Branch name: renovate/registry.access.redhat.com-ubi8-ubi-minimal-8.x
  • Merge into: main
  • Upgrade registry.access.redhat.com/ubi8/ubi-minimal to 8.10-1255
Update k8s.gcr.io/sig-storage/csi-node-driver-registrar Docker tag to v2.13.0
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.gcr.io-sig-storage-csi-node-driver-registrar-2.x
  • Merge into: main
  • Upgrade k8s.gcr.io/sig-storage/csi-node-driver-registrar to v2.13.0
Update k8s.gcr.io/sig-storage/csi-provisioner Docker tag to v5.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.gcr.io-sig-storage-csi-provisioner-5.x
  • Merge into: main
  • Upgrade k8s.gcr.io/sig-storage/csi-provisioner to v5.2.0
Update module golang.org/x/net to v0.40.0
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-net-0.x
  • Merge into: main
  • Upgrade golang.org/x/net to v0.40.0
Update module google.golang.org/grpc to v1.72.0
  • Schedule: ["at any time"]
  • Branch name: renovate/google.golang.org-grpc-1.x
  • Merge into: main
  • Upgrade google.golang.org/grpc to v1.72.0
Update registry.k8s.io/sig-storage/livenessprobe Docker tag to v2.15.0
  • Schedule: ["at any time"]
  • Branch name: renovate/registry.k8s.io-sig-storage-livenessprobe-2.x
  • Merge into: main
  • Upgrade registry.k8s.io/sig-storage/livenessprobe to v2.15.0
Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
Update softprops/action-gh-release action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/softprops-action-gh-release-2.x
  • Merge into: main
  • Upgrade softprops/action-gh-release to v2

🚸 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 icr.io/ibm/ibm-object-csi-driver

Files affected: deploy/ibmCloud/kustomization.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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants