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

• go.mod (gomod)
• tools/check/go.mod (gomod)

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

fix(deps): update github.com/kami-zh/go-capturer digest to 52ea6c8

• Schedule: ["at any time"]
• Branch name: renovate/github.com-kami-zh-go-capturer-digest
• Merge into: master
• Upgrade github.com/kami-zh/go-capturer to 52ea6c8fed04b316685a3b1a57bb8b46b406f929

fix(deps): update github.com/pingcap/log digest to a0d097d

• Schedule: ["at any time"]
• Branch name: renovate/github.com-pingcap-log-digest
• Merge into: master
• Upgrade github.com/pingcap/log to a0d097d16e22ce534e3ecb62bdf8563276b24435

fix(deps): update github.com/pingcap/tidb/parser digest to 60784a3

• Schedule: ["at any time"]
• Branch name: renovate/github.com-pingcap-tidb-parser-digest
• Merge into: master
• Upgrade github.com/pingcap/tidb/parser to 60784a30d041479769aa6a4a351df5eeddd0d94a

fix(deps): update github.com/pingcap/tipb digest to aa19c2d

• Schedule: ["at any time"]
• Branch name: renovate/github.com-pingcap-tipb-digest
• Merge into: master
• Upgrade github.com/pingcap/tipb to aa19c2d12587e66b31069f790fc371b6be565504

fix(deps): update github.com/syndtr/goleveldb digest to 126854a

• Schedule: ["at any time"]
• Branch name: renovate/github.com-syndtr-goleveldb-digest
• Merge into: master
• Upgrade github.com/syndtr/goleveldb to 126854af5e6d8295ef8e8bee3040dd8380ae72e8

fix(deps): update github.com/tikv/pd/client digest to 9a3af11

• Schedule: ["at any time"]
• Branch name: renovate/github.com-tikv-pd-client-digest
• Merge into: master
• Upgrade github.com/tikv/pd/client to 9a3af1191d97292b4ea57aaf55415262282a8a2c

fix(deps): update module github.com/dustin/go-humanize to v1.0.1

• Schedule: ["at any time"]
• Branch name: renovate/github.com-dustin-go-humanize-1.x
• Merge into: master
• Upgrade github.com/dustin/go-humanize to v1.0.1

fix(deps): update module github.com/go-sql-driver/mysql to v1.7.1

• Schedule: ["at any time"]
• Branch name: renovate/github.com-go-sql-driver-mysql-1.x
• Merge into: master
• Upgrade github.com/go-sql-driver/mysql to v1.7.1

fix(deps): update module github.com/golang/protobuf to v1.5.3

• Schedule: ["at any time"]
• Branch name: renovate/github.com-golang-protobuf-1.x
• Merge into: master
• Upgrade github.com/golang/protobuf to v1.5.3

fix(deps): update module github.com/tikv/client-go/v2 to v2.0.7

• Schedule: ["at any time"]
• Branch name: renovate/github.com-tikv-client-go-v2-2.x
• Merge into: master
• Upgrade github.com/tikv/client-go/v2 to c853ddc68c41ff9dad1ed8ce11c3f062a84bf220

fix(deps): update module go.etcd.io/etcd/client/v3 to v3.5.9

• Schedule: ["at any time"]
• Branch name: renovate/go.etcd.io-etcd-client-v3-3.x
• Merge into: master
• Upgrade go.etcd.io/etcd/client/v3 to v3.5.9

fix(deps): update module go.etcd.io/etcd/tests/v3 to v3.5.9

• Schedule: ["at any time"]
• Branch name: renovate/go.etcd.io-etcd-tests-v3-3.x
• Merge into: master
• Upgrade go.etcd.io/etcd/tests/v3 to v3.5.9

fix(deps): update module github.com/burntsushi/toml to v1.3.2

• Schedule: ["at any time"]
• Branch name: renovate/github.com-burntsushi-toml-1.x
• Merge into: master
• Upgrade github.com/BurntSushi/toml to v1.3.2

fix(deps): update module github.com/godror/godror to v0.37.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-godror-godror-0.x
• Merge into: master
• Upgrade github.com/godror/godror to v0.37.0

fix(deps): update module github.com/google/gofuzz to v1.2.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-google-gofuzz-1.x
• Merge into: master
• Upgrade github.com/google/gofuzz to v1.2.0

fix(deps): update module github.com/prometheus/client_golang to v1.16.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-prometheus-client_golang-1.x
• Merge into: master
• Upgrade github.com/prometheus/client_golang to v1.16.0

fix(deps): update module github.com/prometheus/client_model to v0.4.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-prometheus-client_model-0.x
• Merge into: master
• Upgrade github.com/prometheus/client_model to v0.4.0

fix(deps): update module github.com/shopify/sarama to v1.38.1

• Schedule: ["at any time"]
• Branch name: renovate/github.com-shopify-sarama-1.x
• Merge into: master
• Upgrade github.com/Shopify/sarama to v1.38.1

fix(deps): update module github.com/unrolled/render to v1.6.0

• Schedule: ["at any time"]
• Branch name: renovate/github.com-unrolled-render-1.x
• Merge into: master
• Upgrade github.com/unrolled/render to v1.6.0

fix(deps): update module golang.org/x/net to v0.11.0

• Schedule: ["at any time"]
• Branch name: renovate/golang.org-x-net-0.x
• Merge into: master
• Upgrade golang.org/x/net to v0.11.0

fix(deps): update module golang.org/x/sync to v0.3.0

• Schedule: ["at any time"]
• Branch name: renovate/golang.org-x-sync-0.x
• Merge into: master
• Upgrade golang.org/x/sync to v0.3.0

fix(deps): update module golang.org/x/sys to v0.9.0

• Schedule: ["at any time"]
• Branch name: renovate/golang.org-x-sys-0.x
• Merge into: master
• Upgrade golang.org/x/sys to v0.9.0

fix(deps): update module google.golang.org/grpc to v1.56.1

• Schedule: ["at any time"]
• Branch name: renovate/google.golang.org-grpc-1.x
• Merge into: master
• Upgrade google.golang.org/grpc to v1.56.1

fix(deps): update module github.com/pingcap/kvproto to v5

• Schedule: ["at any time"]
• Branch name: renovate/github.com-pingcap-kvproto-5.x
• Merge into: master
• Upgrade github.com/pingcap/kvproto to 7790f94ac2ad2a1141fc63089e335135e79d1961

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

---

⚠ Dependency Lookup Warnings ⚠

Please correct - or verify that you can safely ignore - these lookup failures before you merge this PR.

• Could not determine new digest for update (datasource: go)

Files affected: go.mod

---

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

[ti-chi-bot]

[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 3aceshowhand for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[ti-chi-bot]

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

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

Details

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.

[wuhuizuo]

/ok-to-test

[wuhuizuo]

/release-note-none

[wuhuizuo]

/test ?

[ti-chi-bot]

@wuhuizuo: The following commands are available to trigger required jobs:

• /test wip-pull-unit-test

Details

In response to this:

/test ?

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.

[wuhuizuo]

/test wip-pull-unit-test

[wuhuizuo]

/test wip-pull-unit-test

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (master@30a49bc). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff            @@
##             master    #1260   +/-   ##
=========================================
  Coverage          ?   47.76%           
=========================================
  Files             ?       98           
  Lines             ?    12905           
  Branches          ?        0           
=========================================
  Hits              ?     6164           
  Misses            ?     6191           
  Partials          ?      550           

Flag	Coverage Δ
unit	47.76% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[pingcap-cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}