-
Notifications
You must be signed in to change notification settings - Fork 3
docs: update changelog 3.13.0 #977
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Pull request overview
This pull request updates the changelog documentation for Bytebase version 3.13.0, released on December 18, 2025. The changes refine descriptions, improve clarity, add documentation links, and reorganize bullet points for better logical flow.
Key changes:
- Enhanced description to include simplified approval flow configuration
- Improved clarity and detail in notable changes descriptions
- Added documentation links for new features (MCP integration and GitHub Actions support)
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - SQL review rules use typed payload fields (`number_payload`, `string_payload`, `string_array_payload`, `naming_payload`, etc.). | ||
| - Generic payload and comment fields are removed. | ||
| - Rule level enums migrate from `SQLReviewRuleLevel_WARNING/ERROR` to `SQLReviewRule_WARNING/ERROR`. | ||
| - Move rollout policy checkers from environment to project level: **Require issue approval** and **Plan check enforcement**. Project settings are checked if any checker is previously used via automatic migration. |
Copilot
AI
Dec 24, 2025
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.
Missing space after "project level:" - there should be a space before the list of checkers begins. The sentence reads awkwardly; consider rephrasing to "Move rollout policy checkers (Require issue approval and Plan check enforcement) from environment to project level. Project settings are checked if any checker was previously used via automatic migration."
| - Move rollout policy checkers from environment to project level: **Require issue approval** and **Plan check enforcement**. Project settings are checked if any checker is previously used via automatic migration. | |
| - Move rollout policy checkers (**Require issue approval** and **Plan check enforcement**) from environment to project level. Project settings are checked if any checker was previously used via automatic migration. |
Co-authored-by: Copilot <[email protected]>
No description provided.