Skip to content
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

Configure Renovate #899

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

Conversation

renovate-bot
Copy link

@renovate-bot renovate-bot commented May 3, 2024

Mend 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

  • WORKSPACE (bazel)
  • bazel/bazel_rules_python.bzl (bazel)
  • bazel/googleapis.bzl (bazel)
  • .bazelversion (bazelisk)
  • docker/cloudbuild.yaml (cloudbuild)
  • docker/Dockerfile-envoy (dockerfile)
  • docker/Dockerfile-gcsrunner.tmpl (dockerfile)
  • docker/Dockerfile-prow-env (dockerfile)
  • docker/Dockerfile-proxy.tmpl (dockerfile)
  • docker/Dockerfile-serverless.tmpl (dockerfile)
  • go.mod (gomod)
  • package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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 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 25 Pull Requests:

Update module golang.org/x/net to v0.23.0 [SECURITY]
  • Branch name: renovate/go-golang.org/x/net-vulnerability
  • Merge into: master
  • Upgrade golang.org/x/net to v0.23.0
Update module google.golang.org/grpc to v1.56.3 [SECURITY]
  • Branch name: renovate/go-google.golang.org/grpc-vulnerability
  • Merge into: master
  • Upgrade google.golang.org/grpc to v1.56.3
Update module google.golang.org/protobuf to v1.33.0 [SECURITY]
  • Branch name: renovate/go-google.golang.org/protobuf-vulnerability
  • Merge into: master
  • Upgrade google.golang.org/protobuf to v1.33.0
Update com_github_googleapis_googleapis digest to d44c300
  • Schedule: ["at any time"]
  • Branch name: renovate/com_github_googleapis_googleapis-digest
  • Merge into: master
  • Upgrade com_github_googleapis_googleapis to d44c3001960c430bc60ac1e1736cebfd8fd45e77
Update github.com/google/brotli/go/cbrotli digest to 39bcecf
Update google.golang.org/genproto digest to d784300
  • Schedule: ["at any time"]
  • Branch name: renovate/google.golang.org-genproto-digest
  • Merge into: master
  • Upgrade google.golang.org/genproto to d784300faade
Update zlib digest to ceadaf2
  • Schedule: ["at any time"]
  • Branch name: renovate/zlib-digest
  • Merge into: master
  • Upgrade zlib to ceadaf28dfa48dbf238a0ddb884d4c543b4170e8
Update module github.com/golang/protobuf to v1.5.4
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-golang-protobuf-1.x
  • Merge into: master
  • Upgrade github.com/golang/protobuf to v1.5.4
Update module github.com/gorilla/mux to v1.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-gorilla-mux-1.x
  • Merge into: master
  • Upgrade github.com/gorilla/mux to v1.8.1
Update module github.com/imdario/mergo to v0.3.16
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-imdario-mergo-0.x
  • Merge into: master
  • Upgrade github.com/imdario/mergo to v0.3.16
Update module github.com/miekg/dns to v1.1.61
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-miekg-dns-1.x
  • Merge into: master
  • Upgrade github.com/miekg/dns to v1.1.61
Update alpine Docker tag to v3.20
  • Schedule: ["at any time"]
  • Branch name: renovate/alpine-3.x
  • Merge into: master
  • Upgrade alpine to 3.20
Update dependency bazel to v6.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/bazel-6.x
  • Merge into: master
  • Upgrade bazel to 6.5.0
Update dependency io_bazel_rules_python to v0.34.0
  • Schedule: ["at any time"]
  • Branch name: renovate/io_bazel_rules_python-0.x
  • Merge into: master
  • Upgrade io_bazel_rules_python to 0.34.0
Update module cloud.google.com/go/storage to v1.43.0
  • Schedule: ["at any time"]
  • Branch name: renovate/cloud.google.com-go-storage-1.x
  • Merge into: master
  • Upgrade cloud.google.com/go/storage to v1.43.0
Update module github.com/envoyproxy/go-control-plane to v0.12.0
Update module github.com/golang/glog to v1.2.2
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-golang-glog-1.x
  • Merge into: master
  • Upgrade github.com/golang/glog to v1.2.2
Update module github.com/google/go-cmp to v0.6.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.6.0
Update module github.com/gorilla/websocket to v1.5.3
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-gorilla-websocket-1.x
  • Merge into: master
  • Upgrade github.com/gorilla/websocket to v1.5.3
Update module golang.org/x/oauth2 to v0.21.0
  • Schedule: ["at any time"]
  • Branch name: renovate/golang.org-x-oauth2-0.x
  • Merge into: master
  • Upgrade golang.org/x/oauth2 to v0.21.0
Update module google.golang.org/api to v0.189.0
  • Schedule: ["at any time"]
  • Branch name: renovate/google.golang.org-api-0.x
  • Merge into: master
  • Upgrade google.golang.org/api to v0.189.0
Update debian Docker tag to v12
  • Schedule: ["at any time"]
  • Branch name: renovate/debian-12.x
  • Merge into: master
  • Upgrade debian to bookworm
Update dependency bazel to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/bazel-7.x
  • Merge into: master
  • Upgrade bazel to 7.2.1
Update module github.com/envoyproxy/protoc-gen-validate to v1
Update module github.com/imdario/mergo to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-imdario-mergo-1.x
  • Merge into: master
  • Upgrade github.com/imdario/mergo to v1.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.


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

Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: renovate-bot
Once this PR has been reviewed and has the lgtm label, please assign shuoyang2016 for approval. For more information see the Kubernetes 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

Hi @renovate-bot. Thanks for your PR.

I'm waiting for a GoogleCloudPlatform 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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant