deps,version: bump client-go for nextgen 202603#5311
Conversation
Bump client-go to the latest release-nextgen-202603-ticdc.
Raise the maximum compatible TiKV version boundary to 26.4.0 for the nextgen release branch.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the github.com/tikv/client-go/v2 dependency in go.mod and go.sum. Additionally, it increases the maximum compatible TiKV version (maxTiKVVersion) from 15.0.0 to 26.4.0 in pkg/version/check.go. There are no review comments to address, and I have no additional feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
/test next-gen |
What problem does this PR solve?
Issue Number: ref #5206
This is a release-nextgen-202603 follow-up to #5205.
The release-nextgen-202603 branch needs to consume the latest TiCDC-specific
github.com/tikv/client-go/v2branch revision for nextgen shared-lock related fixes: tikv/client-go#2000The branch also needs the TiKV compatibility upper bound aligned with the nextgen release version range.
What is changed and how it works?
github.com/tikv/client-go/v2fromv2.0.8-0.20260609065146-a68b42e6aab4tov2.0.8-0.20260610130222-a41cab3aaf31.go.sumwith the new client-go checksum.maxTiKVVersionfrom15.0.0to26.4.0.Check List
Tests
Local checks run:
go mod tidygit diff --check upstream/release-nextgen-202603..HEADGOCACHE=/tmp/ticdc-go-cache go test ./pkg/versionGOCACHE=/tmp/ticdc-go-cache make cdcQuestions
Will it cause performance regression or break compatibility?
No expected performance regression. The dependency bump is limited to the TiCDC-specific client-go branch for nextgen shared-lock fixes, and the version compatibility bound is adjusted for the nextgen release range.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note