build(deps): bump client-go to include pd#10522

[okJiang]

What problem does this PR solve?

Issue Number: ref #67511,

ref tikv/pd#10522, ref tikv/client-go#1935

Problem Summary:
TiDB should consume the merged upstream client-go change that includes the RM fallback warning-spam fix from tikv/pd#10522.

What changed and how does it work?

• bump github.com/tikv/client-go/v2 to v2.0.8-0.20260401083018-b7f9a9e9d2ab, which is the merged upstream commit from tikv/client-go#1935
• keep the resolved github.com/tikv/pd/client version at v0.0.0-20260401072359-048f0d8f6f71
• refresh DEPS.bzl so Bazel fetches the upstream client-go artifact instead of the temporary fork artifact used earlier in this PR

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Manual test steps:

• go mod tidy
• make bazel_prepare
• go test -run TestNonExistent ./br/pkg/... ./lightning/pkg/... ./dumpling/export
• go list ./cmd/tidb-server ./pkg/store/... ./pkg/server/... ./pkg/session/... ./pkg/executor/... ./pkg/planner/... | rg -v '/test/|/tests/|_test$|^github.com/pingcap/tidb/pkg/planner/implementation$' | xargs -n 40 go test -run TestNonExistent

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

Summary by CodeRabbit

• Chores
  • Updated TiKV client dependencies to latest versions for improved stability.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated pinned versions of two TiKV dependencies across Go and Bazel manifests. The github.com/tikv/client-go/v2 dependency advanced to commit b7f9a9e9d2ab, and github.com/tikv/pd/client advanced to commit 048f0d8f6f71, with corresponding checksums and mirror URLs refreshed.

Changes

Cohort / File(s)	Summary
Dependency Version Updates DEPS.bzl, go.mod	Updated pinned versions of com_github_tikv_client_go_v2 and com_github_tikv_pd_client with new commit hashes, sha256 checksums, and mirrored download URLs.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly Related PRs

• txn: Fix and add test for the issue that transaction using fair locking multiple times in the first statement may make keeping-alive fail (#67141) #67234: Updates the same github.com/tikv/client-go/v2 dependency in both go.mod and DEPS.bzl to an aligned version.
• *: revert bump client to latest | tidb-test=release-8.5-20260121-v8.5.5 pd=release-8.5-20260121-v8.5.5 #67078: Modifies the same go_repository entries (com_github_tikv_client_go_v2 and com_github_tikv_pd_client) in DEPS.bzl and corresponding module pins in go.mod.
• chore: bump pd client to include resourcegroup signal-aware wait fix #67428: Updates the github.com/tikv/pd/client dependency in both DEPS.bzl and go.mod to a newer commit.

Suggested Labels

ok-to-test, approved, lgtm

Suggested Reviewers

• lcwangchao
• YuJuncen
• xhebox

Poem

🐰 Two hoppy bumps along the way,
TiKV deps get fresh today!
Checksums dance, commits align,
The mirrors gleam in manifest shine! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: bumping the client-go dependency to include a specific upstream fix (pd#10522). It is concise and specific.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The PR description follows the required template with Issue Number, Problem Summary, What Changed sections, and a comprehensive Check List including test selection and release notes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[tiprow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[pantheon-ai]

@okJiang I've received your pull request and will start the review. I'll conduct a thorough review covering code quality, potential issues, and implementation details.

⏳ This process typically takes 10-30 minutes depending on the complexity of the changes.

_{ℹ️ Learn more details on Pantheon AI.}

[okJiang]

/retest

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.6260%. Comparing base (dcf6f03) to head (e103bfe).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #67491        +/-   ##
================================================
- Coverage   77.7878%   77.6260%   -0.1618%     
================================================
  Files          1959       1945        -14     
  Lines        543377     545063      +1686     
================================================
+ Hits         422681     423111       +430     
- Misses       119855     121949      +2094     
+ Partials        841          3       -838     

Flag	Coverage Δ
integration	41.0993% <ø> (+4.9245%)	⬆️
unit	76.8097% <ø> (+0.3693%)	⬆️

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

Components	Coverage Δ
dumpling	61.5065% <ø> (ø)
parser	∅ <ø> (∅)
br	48.9178% <ø> (-12.0727%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[okJiang]

/retest

[okJiang]

/check-issue-triage-complete

[ti-chi-bot]

@lhy1024: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

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.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-04-03 02:12:39.214425771 +0000 UTC m=+490364.419785818: ☑️ agreed by YuJuncen.
• 2026-04-03 03:03:29.671611867 +0000 UTC m=+493414.876971924: ☑️ agreed by cfzjywxk.

[bb7133]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133, cfzjywxk, lhy1024, YuJuncen

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [YuJuncen,bb7133,cfzjywxk]

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

[okJiang]

/retest

[okJiang]

/retest

[okJiang]

/cherry-pick release-nextgen-202603

[ti-chi-bot]

@okJiang: new pull request created to branch release-nextgen-202603: #67602.

Details

In response to this:

/cherry-pick release-nextgen-202603

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 ti-community-infra/tichi repository.