-
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -2,24 +2,26 @@ | |||||
| title: Bytebase 3.13.0 - Dec 18, 2025 | ||||||
| author: Adela | ||||||
| updated_at: 2025/12/18 18:00:00 | ||||||
| description: 'Support MCP integration' | ||||||
| description: 'Support MCP integration and simplified approval flow configuration' | ||||||
| --- | ||||||
|
|
||||||
| import InstallUpgrade from '/snippets/install/install-upgrade.mdx'; | ||||||
|
|
||||||
| ## 🔔 Notable Changes | ||||||
|
|
||||||
| - **Consolidate DDL and DML changes** so users no longer need to select them explicitly. | ||||||
| - Update SQL review configuration for Terraform: (e.g. [sql_review.tf](https://github.com/bytebase/terraform-provider-bytebase/blob/main/examples/setup/sql_review.tf)) | ||||||
| - 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 from `SQLReviewRuleLevel_WARNING/ERROR` to `SQLReviewRule_WARNING/ERROR`. | ||||||
| - **Consolidate DDL and DML changes** so users no longer need to select them explicitly when initiating New Plan or configuring approval flow. | ||||||
| - **Simplify approval workflows**: | ||||||
| - Approval flows are defined directly using CEL expressions, without intermediate risk definitions. | ||||||
| - Risk evaluation uses system presets. | ||||||
| - Risk level is automatically evaluated using a standardized assessment framework. | ||||||
| - `risk.level` is an optional CEL factor for CHANGE_DATABASE approval flows. | ||||||
| - For non-Terraform, existing approval flows are automatically migrated. | ||||||
| - For Terraform, approval flows are defined via bytebase_setting (settings/WORKSPACE_APPROVAL) using approval_flow.rules.flow, and risk resources are removed.(e.g. [approval_flow.tf](https://github.com/bytebase/terraform-provider-bytebase/blob/main/examples/setup/approval_flow.tf)) | ||||||
| - Move rollout policy checkers (**Require issue approval**, **Plan check enforcement**) from environment to project. | ||||||
| - Update SQL review configuration for Terraform: (e.g. [sql_review.tf](https://github.com/bytebase/terraform-provider-bytebase/blob/main/examples/setup/sql_review.tf)) | ||||||
| - 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. | ||||||
|
||||||
| - 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. |
Uh oh!
There was an error while loading. Please reload this page.