World's most advanced database DevSecOps solution for Developer, Security, DBA and Platform Engineering teams. The GitHub/GitLab for database DevSecOps.
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 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)
Update SQL review configuration for Terraform: (e.g. )
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.
Migrate user identifiers: User references change from users/{id} to users/{email} in APIs and storage. Audit logs store user emails directly.
Rename Masking Exception to Masking Exemption:
APIs rename MaskingException to MaskingExemption.
The action field is removed.
member is replaced with a members list.
For Terraform, masking_exception_policy is renamed to masking_exemption_policy.
Disallow Copy Policy now applies to Admin and DBA roles (previously exempted).
Refine database group permissions:
Roles with bb.projects.get gain bb.databaseGroups.list/get.
Roles with bb.projects.update gain bb.databaseGroups.create/update/delete.
For Terraform, please update the permissions of custom roles accordingly.
Update batch task APIs: The reason field is removed from BatchRunTasks and BatchCancelTaskRuns. reason is supported only for skip operations.
Warning 1): Bytebase does not support in-place downgrade. Make sure to back up your metadata before upgrading. 2) Never run multiple containers on the same data directory. Stop and remove the old one first to avoid corruption.