Skip to content

chore: Configure Renovate #860

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: master
Choose a base branch
from
Open

chore: Configure Renovate #860

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 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

  • Containerfile.plugin (dockerfile)
  • Dockerfile (dockerfile)
  • openshift-ci/build-root/Dockerfile (dockerfile)
  • openshift-ci/build-root/source-image/Dockerfile (dockerfile)
  • .github/workflows/codegen.yaml (github-actions)
  • .github/workflows/openshift-ci-automation.yaml (github-actions)
  • go.mod (gomod)
  • hack/upgrade-rollouts-manager/go.mod (gomod)
  • 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
  • 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 23 Pull Requests:

fix(deps): update module github.com/argoproj/argo-cd/v2 to v2.13.8 [security]
chore(deps): update github.com/go-check/check digest to 10cb982
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-go-check-check-digest
  • Merge into: master
  • Upgrade github.com/go-check/check to 10cb98267c6c
fix(deps): update github.com/argoproj-labs/argo-rollouts-manager digest to 9571119
fix(deps): update github.com/openshift/api digest to 7941651
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-openshift-api-digest
  • Merge into: master
  • Upgrade github.com/openshift/api to 79416512cdcbe5b90d40e77327260863e26487d0
fix(deps): update k8s.io/utils digest to 4c0f3b2
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-utils-digest
  • Merge into: master
  • Upgrade k8s.io/utils to 4c0f3b243397
fix(deps): update module github.com/argoproj-labs/argocd-operator to v0.14.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-argoproj-labs-argocd-operator-0.x
  • Merge into: master
  • Upgrade github.com/argoproj-labs/argocd-operator to a95e322d75caa263296927203484610ec5358bda
fix(deps): update module github.com/argoproj/gitops-engine to v0.7.3
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-argoproj-gitops-engine-0.x
  • Merge into: master
  • Upgrade github.com/argoproj/gitops-engine to 3516b3928a06c7d04c200f06beaf04b3c2bef63f
fix(deps): update module github.com/go-logr/logr to v1.4.3
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-go-logr-logr-1.x
  • Merge into: master
  • Upgrade github.com/go-logr/logr to v1.4.3
chore(deps): update dependency go to v1.24.4
  • Schedule: ["at any time"]
  • Branch name: renovate/go-1.x
  • Merge into: master
  • Upgrade go to 1.24.4
chore(deps): update golang docker tag to v1.24
  • Schedule: ["at any time"]
  • Branch name: renovate/golang-1.x
  • Merge into: master
  • Upgrade golang to 1.24
chore(deps): update module k8s.io/dynamic-resource-allocation to v0.33.1
chore(deps): update module k8s.io/endpointslice to v0.33.1
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-endpointslice-0.x
  • Merge into: master
  • Upgrade k8s.io/endpointslice to v0.33.1
chore(deps): update module k8s.io/kms to v0.33.1
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-kms-0.x
  • Merge into: master
  • Upgrade k8s.io/kms to v0.33.1
fix(deps): update kubernetes packages
fix(deps): update module github.com/google/go-cmp to v0.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-google-go-cmp-0.x
  • Merge into: master
  • Upgrade github.com/google/go-cmp to v0.7.0
fix(deps): update module github.com/hashicorp/go-version to v1.7.0
fix(deps): 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: master
  • Upgrade github.com/onsi/ginkgo/v2 to v2.23.4
fix(deps): 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
fix(deps): update module github.com/operator-framework/api to v0.31.0
fix(deps): update module github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring to v0.83.0
fix(deps): update module golang.org/x/mod to v0.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-mod-0.x
  • Merge into: master
  • Upgrade golang.org/x/mod to v0.25.0
fix(deps): update module sigs.k8s.io/controller-runtime to v0.21.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.21.0
fix(deps): update module github.com/google/go-github/v58 to v72
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-google-go-github-v58-72.x
  • Merge into: master
  • Upgrade github.com/google/go-github/v58 to v72.0.0

🚸 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 registry.redhat.io/rhel8/go-toolset

Files affected: Containerfile.plugin


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

@openshift-ci openshift-ci bot requested review from anandrkskd and keithchong March 7, 2025 04:24
Copy link

openshift-ci bot commented Mar 7, 2025

[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 sbose78 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:

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

Copy link

openshift-ci bot commented Mar 7, 2025

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

I'm waiting for a redhat-developer 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.

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.

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

Successfully merging this pull request may close these issues.

0 participants