tiflash-proxy-next-gen: bind data key id from encryption meta

[hbisheng]

What problem does this PR solve?

Issue Number: ref #10952

Problem Summary:

What is changed and how it works?

Bump submodule contrib/tiflash-proxy-next-gen to pick up next-gen proxy data key id binding from encryption meta.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  • Tested tiflash write can read data key generated by latest-release-tikv.
• No code

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 a bundled subproject to a newer revision, which may include underlying improvements and fixes.

[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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7473511b-4127-48a2-968e-322ba3bac0f3

📥 Commits

Reviewing files that changed from the base of the PR and between 63cff9a and e6f633b.

📒 Files selected for processing (1)

• contrib/tiflash-proxy-next-gen

---

📝 Walkthrough

Walkthrough

This PR updates the contrib/tiflash-proxy-next-gen submodule reference to a new commit hash, replacing the previous commit pointer.

Changes

Submodule Update

Layer / File(s)	Summary
Submodule commit bump contrib/tiflash-proxy-next-gen	Updates the subproject commit pointer from 5fa3872069ec9ee85a9faf633030a0ee9d090197 to 45187f537fd50287eb46d067960d00d7adbdb11e.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• pingcap/tiflash#10884: Both PRs update the contrib/tiflash-proxy-next-gen submodule pointer to different commit targets.

Suggested reviewers: yongman, Lloyd-Pottiger

Poem

A tiny hop, a pointer new,
One commit hash traded for a view,
The proxy sleeps in updated code,
While this rabbit thumps the road. 🐇
Onward to the next-gen burrow we go!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the main change: a tiflash-proxy-next-gen bump to bind data key IDs from encryption metadata.
Description check	✅ Passed	The description mostly follows the template with issue reference, summary, tests, side effects, docs, and release note sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ 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.}

[hbisheng]

/test pull-sanitizer-asan

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, yongman

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 [JaySon-Huang,yongman]

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]

[LGTM Timeline notifier]

Timeline:

• 2026-07-03 03:54:35.233515203 +0000 UTC m=+357216.933894635: ☑️ agreed by yongman.
• 2026-07-03 04:21:52.361640007 +0000 UTC m=+358854.062019430: ☑️ agreed by JaySon-Huang.

[JaySon-Huang]

/cherry-pick release-nextgen-20251011

[ti-chi-bot]

@JaySon-Huang: once the present PR merges, I will cherry-pick it on top of release-nextgen-20251011 in the new PR and assign it to you.

Details

In response to this:

/cherry-pick release-nextgen-20251011

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.

[JaySon-Huang]

/cherry-pick release-nextgen-202603

[ti-chi-bot]

@JaySon-Huang: once the present PR merges, I will cherry-pick it on top of release-nextgen-202603 in the new PR and assign it to you.

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.

[hbisheng]

/retest

[ti-chi-bot]

@JaySon-Huang: failed to apply #10948 on top of branch "release-nextgen-20251011":

[failed to git add conflicting files: exit status 128, failed to git commit: exit status 128]

Details

In response to this:

/cherry-pick release-nextgen-20251011

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.

[ti-chi-bot]

@JaySon-Huang: new pull request created to branch release-nextgen-202603: #10953.

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.