cloud: add 20260115 release notes #22331
Conversation
ti-chi-bot
bot
added
missing-translation-status
Summary of ChangesHello @qiancai, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request systematically updates the TiDB Cloud documentation by archiving the 2025 release notes into a dedicated file and preparing the main release notes page for 2026. It also ensures that the FAQ section accurately reflects the most current default TiDB version for Dedicated clusters, providing a clear and up-to-date reference for users. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
qiancai
added
area/tidb-cloud
![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 adds a new release note for January 15, 2026, and archives the 2025 release notes into a new file. The changes are generally good, but I've identified a few areas for improvement. I've left comments regarding minor formatting issues like extra spaces in tidb-cloud/release-notes-2025.md. More importantly, in tidb-cloud-release-notes.md, there's a typo in the year, and the aliases frontmatter has been removed, which could lead to broken links. Please review the detailed comments for suggestions.
|
|
||
| How to try it: | ||
|
|
||
| - From the [TiDB Cloud console](https://tidbcloud.com/), choose Alibaba Cloud as the cloud provider when creating a cluster to view the Essential option. |
There was a problem hiding this comment.
There's a double space after provider. Please remove it for better formatting and consistency.
| - From the [TiDB Cloud console](https://tidbcloud.com/), choose Alibaba Cloud as the cloud provider when creating a cluster to view the Essential option. | |
| - From the [TiDB Cloud console](https://tidbcloud.com/), choose Alibaba Cloud as the cloud provider when creating a cluster to view the Essential option. |
|
|
||
| **General changes** | ||
|
|
||
| - For [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters, the maximum storage size of TiKV nodes with 16 vCPU and 32 vCPU is changed from **6144 GiB** to **4096 GiB**. |
There was a problem hiding this comment.
There's a trailing space at the end of this line. Please remove it to maintain consistent formatting.
| - For [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters, the maximum storage size of TiKV nodes with 16 vCPU and 32 vCPU is changed from **6144 GiB** to **4096 GiB**. | |
| - For [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters, the maximum storage size of TiKV nodes with 16 vCPU and 32 vCPU is changed from **6144 GiB** to **4096 GiB**. |
|
|
||
| **General changes** | ||
|
|
||
| - [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) on Microsoft Azure is now available in public preview. |
There was a problem hiding this comment.
There's a trailing space at the end of this line. Please remove it to maintain consistent formatting.
| - [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) on Microsoft Azure is now available in public preview. | |
| - [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) on Microsoft Azure is now available in public preview. |
|
|
||
| **General changes** | ||
|
|
||
| - Data export to Alibaba Cloud OSS is now supported. |
There was a problem hiding this comment.
There's a trailing space at the end of this line. Please remove it to maintain consistent formatting.
| - Data export to Alibaba Cloud OSS is now supported. | |
| - Data export to Alibaba Cloud OSS is now supported. |
|
|
||
| **General changes** | ||
|
|
||
| - Support creating TiDB node groups for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters to enhance resource management flexibility. |
There was a problem hiding this comment.
There's a trailing space at the end of this line. Please remove it to maintain consistent formatting.
| - Support creating TiDB node groups for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters to enhance resource management flexibility. | |
| - Support creating TiDB node groups for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters to enhance resource management flexibility. |
|
|
||
| - Support using the Debezium protocol. Debezium is a tool for capturing database changes. It converts each captured database change into a message called an event, and sends these events to Kafka. For more information, see [TiCDC Debezium Protocol](https://docs.pingcap.com/tidb/v8.1/ticdc-debezium). | ||
|
|
||
| - Support defining a single partition dispatcher for all tables, or different partition dispatchers for different tables. |
There was a problem hiding this comment.
There's a trailing space at the end of this line. Please remove it to maintain consistent formatting.
| - Support defining a single partition dispatcher for all tables, or different partition dispatchers for different tables. | |
| - Support defining a single partition dispatcher for all tables, or different partition dispatchers for different tables. |
qiancai
changed the title
[LGTM Timeline notifier]Timeline:
|
qiancai
changed the title
qiancai
changed the title
|
@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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai 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 |
|
/retest |
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?