8000 Configure Renovate by gardener-ci-robot · Pull Request #769 · gardener/etcd-druid · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Configure Renovate #769

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Configure Renovate #769

wants to merge 2 commits into from

Conversation

gardener-ci-robot
Copy link
@gardener-ci-robot gardener-ci-robot commented Feb 21, 2024 •
edited
Loading

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/publish-docs.yml (github-actions)
  • api/go.mod (gomod)
  • client/go.mod (gomod)
  • go.mod (gomod)
  • charts/values.yaml (helm-values)

What to Expect

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

Update golang.org/x/exp digest to b6e5de4
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-exp-digest
  • Merge into: master
  • Upgrade golang.org/x/exp to b6e5de432a8b
Update k8s.io/utils digest to 0f33e8f
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-utils-digest
  • Merge into: master
  • Upgrade k8s.io/utils to 0f33e8f1c979
Update sigs.k8s.io/controller-runtime/tools/setup-envtest digest to 1dce621
Update golang Docker tag to v1.24.3
  • Schedule: ["at any time"]
  • Branch name: renovate/golang-1.x
  • Merge into: master
  • Upgrade golang to 1.24.3
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
Update module github.com/gardener/etcd-backup-restore to v0.36.3
Update module github.com/gardener/etcd-druid/api to v0.30.1
Update module github.com/gardener/etcd-druid/client to v0.30.1
Update module golang.org/x/tools to v0.33.0
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-tools-0.x
  • Merge into: master
  • Upgrade golang.org/x/tools to v0.33.0
Update module k8s.io/api to v0.33.1
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-api-0.x
  • Merge into: master
  • Upgrade k8s.io/api to v0.33.1
Update module k8s.io/apimachinery to v0.33.1
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-apimachinery-0.x
  • Merge into: master
  • Upgrade k8s.io/apimachinery to v0.33.1
Update module k8s.io/client-go to v0.33.1
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-client-go-0.x
  • Merge into: master
  • Upgrade k8s.io/client-go to v0.33.1
Update module k8s.io/code-generator to v0.33.1
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-code-generator-0.x
  • Merge into: master
  • Upgrade k8s.io/code-generator to v0.33.1
Update module k8s.io/component-base to v0.33.1
  • Schedule: ["at any time"]
  • Branch name: renovate/k8s.io-component-base-0.x
  • Merge into: master
  • Upgrade k8s.io/component-base to v0.33.1
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
Update module sigs.k8s.io/controller-tools to v0.18.0
  • 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.18.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.

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

@gardener-ci-robot gardener-ci-robot requested a review from a team as a code owner February 21, 2024 14:32
@gardener-robot gardener-robot added the needs/review Needs review label Feb 21, 2024
@gardener-robot
Copy link

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

@gardener-robot gardener-robot added the size/xs Size of pull request is tiny (see gardener-robot robot/bots/size.py) label Feb 21, 2024
@gardener-robot-ci-1 gardener-robot-ci-1 added reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) and removed reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) labels Feb 21, 2024
@oliver-goetz
Copy link
Member

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
Copy link
Contributor

@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
Copy link
Member

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.

@gardener-robot-ci-3 gardener-robot-ci-3 added the reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Feb 29, 2024
@gardener-robot-ci-2 gardener-robot-ci-2 removed the reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Feb 29, 2024
@shreyas-s-rao
Copy link
Contributor

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

@seshachalam-yv
Copy link
Contributor

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
needs/ok-to-test Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD) needs/review Needs review size/xs Size of pull request is tiny (see gardener-robot robot/bots/size.py)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
8 participants
@gardener-ci-robot @gardener-robot @oliver-goetz @shreyas-s-rao @seshachalam-yv @gardener-robot-ci-1 @gardener-robot-ci-2 @gardener-robot-ci-3
0