chore(dashboard): update version to v9.0.0-8efaf2f7

[yibin87]

What problem does this PR solve?

Update TiDB Dashboard to v9.0.0-8efaf2f7.

Issue Number: Close #10699

What is changed and how does it work?

Related tidb-dashboard release: https://github.com/pingcap/tidb-dashboard/releases/tag/v9.0.0-8efaf2f7

• Update scripts/dashboard-version to 9.0.0-8efaf2f7.
• Refresh the TiDB Dashboard Go module pseudo-version in the root module, tests/integrations, and tools.

*: update tidb-dashboard to v9.0.0-8efaf2f7

Check List

Tests

• Manual test (add detailed scripts or steps below)

./scripts/update-dashboard.sh v9.0.0-8efaf2f7
make pd-server

• No code

Release note

None.

[ti-chi-bot]

Hi @yibin87. Thanks for your PR.

I'm waiting for a tikv 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-sigs/prow repository.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR bumps the github.com/pingcap/tidb-dashboard dependency from commit aa6178a60657 to 8efaf2f70a41 across the main module, test integrations, tools, and dashboard version script, ensuring consistent versioning throughout the project.

Changes

Dashboard Dependency Update

Layer / File(s)	Summary
Version synchronization across modules and scripts go.mod, scripts/dashboard-version, tests/integrations/go.mod, tools/go.mod	Primary module, integration test module, tools module, and build script all update the dashboard dependency version identifier to match the same upstream commit, ensuring consistent pinning across the project.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• tikv/pd#10324: Both PRs bump the github.com/pingcap/tidb-dashboard Go module version in the same places (go.mod, tests/integrations/go.mod, and tools/go.mod), so the main PR's dependency update directly overlaps with the retrieved PR's dashboard version bump.
• tikv/pd#10429: Both PRs directly update the github.com/pingcap/tidb-dashboard dependency version in the root and submodule go.mod files (root/tests/tools), so the main PR's dashboard bump continues the same dependency-alignment change as the retrieved PR.

Suggested labels

contribution, size/S, ok-to-test, needs-cherry-pick-release-8.5

Suggested reviewers

• JmPotato
• nolouch

Poem

🐰 A dashboard update hops through the files,
Four versions pinned with joyful smiles,
From one commit hash to the next so new,
Dependencies dance as they always do! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title 'chore(dashboard): update version to v9.0.0-8efaf2f7' clearly and concisely describes the main change—updating the TiDB Dashboard to a specific version across multiple dependency manifests.
Description check	✅ Passed	The PR description follows the required template with all essential sections completed, including issue number, detailed explanation of changes, commit message, check list with tests, and release note.

_{✏️ 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.}

[yibin87]

/retest

[ti-chi-bot]

@yibin87: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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.

[nolouch]

/ok-to-test

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nolouch

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

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-05-21 05:12:22.615382666 +0000 UTC m=+13873.256239469: ☑️ agreed by nolouch.

[nolouch]

/retest

[ti-chi-bot]

@yibin87: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-unit-test-next-gen-2	1099a7b	link	true	/test pull-unit-test-next-gen-2

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.04%. Comparing base (94df6da) to head (1099a7b).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #10698      +/-   ##
==========================================
+ Coverage   79.03%   79.04%   +0.01%     
==========================================
  Files         536      536              
  Lines       73103    73210     +107     
==========================================
+ Hits        57777    57870      +93     
- Misses      11234    11251      +17     
+ Partials     4092     4089       -3     

Flag	Coverage Δ
unittests	79.04% <ø> (+0.01%)	⬆️

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.