-
Notifications
You must be signed in to change notification settings - Fork 701
cloud: add 20250513 release notes #20944
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloud: add 20250513 release notes #20944
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @Oreoxmt, 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!
Summary of Changes
I've reviewed the pull request and it adds the release notes for TiDB Cloud for May 13, 2025. The release notes detail the availability of full-text search (beta) in TiDB Cloud Serverless, an increase in the maximum TiFlash node storage for TiDB Cloud Dedicated clusters, and enhancements to the maintenance window configuration experience.
Highlights
- Full-text search (beta): Full-text search (beta) is now available in TiDB Cloud Serverless for AI applications, enabling retrieval of content by exact keywords.
- Increased TiFlash node storage: The maximum TiFlash node storage has been increased for TiDB Cloud Dedicated clusters, improving analytics data storage capacity and workload scaling efficiency.
- Enhanced maintenance window configuration: The maintenance window configuration experience has been enhanced with intuitive options to configure and reschedule maintenance tasks.
Changelog
- tidb-cloud/tidb-cloud-release-notes.md
- Added release notes for May 13, 2025.
- Described the availability of full-text search (beta) in TiDB Cloud Serverless.
- Detailed the increase in maximum TiFlash node storage for TiDB Cloud Dedicated clusters.
- Explained the enhancements to the maintenance window configuration experience.
Using Gemini Code Assist
The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
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 .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and 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 to provide feedback.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request adds release notes for TiDB Cloud, including new features and enhancements. The changes seem well-organized and informative. However, there are a few minor issues related to grammar, clarity, and style consistency that could be improved.
Summary of Findings
- Readability and Clarity: Several sentences could be rephrased for improved readability and clarity, making the release notes easier to understand for users.
- Style Consistency: Minor inconsistencies in phrasing (e.g., 'see' vs. 'see the') should be addressed to maintain a consistent style throughout the document. [^1]
Merge Readiness
The pull request is almost ready for merging. Addressing the minor issues related to grammar, clarity, and style consistency would further enhance the quality of the release notes. I am unable to approve this pull request, and recommend that others review and approve this code before merging.
70c8ff9
to
573021b
Compare
[LGTM Timeline notifier]Timeline:
|
/approve |
/unhold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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?