cloud: add release notes for 20260414#22748
cloud: add release notes for 20260414#22748ti-chi-bot[bot] merged 20 commits intopingcap:release-8.5from
Conversation
ti-chi-bot
bot
added
the
missing-translation-status
ti-chi-bot
bot
added
the
size/S
hfxsd
added
translation/no-need
ti-chi-bot
bot
removed
the
missing-translation-status
ti-chi-bot
bot
added
the
size/S
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the TiDB Cloud release notes to include new features for April 14, 2026, such as enhanced Top SQL metrics for Dedicated clusters and a unified console experience. The review feedback focuses on improving consistency by using template variables for product plans, adopting active voice, and ensuring correct terminology for TiDB Serverless instances.
Co-authored-by: Grace Cai <qqzczy@126.com>
|
@EmmaDuDu: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn 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
bot
removed
the
size/S
|
/approve |
|
/approve |
|
/approve |
|
/approve |
|
/retest |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hfxsd The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3 participants
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?