dashboard: update version to v20231127.1

[mornyx]

What problem does this PR solve?

Issue Number: Close #7457

What is changed and how does it work?

Update tidb-dashboard to v20231127.1 to introduce component upgrades for security reason

Dashboard release PR: pingcap/tidb-dashboard#1620

Check List

Tests

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

Code changes

• Has the configuration change
• Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tiup:
• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• CabinfeverB
• rleungx

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

Hi @mornyx. 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/test-infra repository.

[codecov]

Codecov Report

Merging #7458 (0ef82b9) into master (82ace6f) will decrease coverage by 0.04%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7458      +/-   ##
==========================================
- Coverage   74.21%   74.17%   -0.04%     
==========================================
  Files         451      451              
  Lines       49692    49692              
==========================================
- Hits        36879    36861      -18     
- Misses       9500     9516      +16     
- Partials     3313     3315       +2     

Flag	Coverage Δ
unittests	74.17% <ø> (-0.04%)	⬇️

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

[rleungx]

/ok-to-test

[ti-chi-bot]

@xiabee: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments.

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

[rleungx]

/merge

[CabinfeverB]

/merge

[ti-chi-bot]

@rleungx: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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

[ti-chi-bot]

@CabinfeverB: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Details

Commit hash: 0ef82b9

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Details

Commit hash: 0ef82b9

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #7460.

[mornyx]

/cherry-pick release-7.1

[ti-chi-bot]

@mornyx: new pull request created to branch release-7.1: #7517.

Details

In response to this:

/cherry-pick release-7.1

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]

@mornyx: cannot checkout 7.5: error checking out 7.5: exit status 1. output: error: pathspec '7.5' did not match any file(s) known to git

Details

In response to this:

/cherry-pick 7.5

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.

[mornyx]

/cherry-pick release-7.5

[ti-chi-bot]

@mornyx: new pull request created to branch release-7.5: #7518.

Details

In response to this:

/cherry-pick release-7.5

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.