| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-01-15 | 5.8 kB | |
| Release 3.14.0 source code.tar.gz | 2026-01-15 | 6.5 MB | |
| Release 3.14.0 source code.zip | 2026-01-15 | 9.0 MB | |
| Totals: 3 Items | 15.5 MB | 0 | |
π Notable Changes
-
Redesign the database CI/CD workflow to align with industry practices (GitHub, GitLab) by clearly separating CI (review) and CD (deployment) phases:
- Issue page now displays plan changes directly - no more context switching between tabs.
- Rollout is now a standalone deployment page, clearly separating review from execution.
- Rollout UI now supports release-based tasks β showing per-file execution status, command duration, and release info in task items.
- Rollout creation: previously rollout is created at the same time when issue is created, but now it's creation is decoupled from issue creation, with 2 creation modes: 1) automatic creation, if issue is approved AND SQL review check pass; 2) user can manually create in other cases (most common case, issue approved BUT review not passed, and there should be an action button).
- As a result of mode 2, project releaser might need to create rollout manually before executing rollout, so
bb.rollouts.createpermission is added to project releaser role. All custom roles for rollout initiation are advised to be assignedbb.rollouts.createpermission. This permission only controls who can create a rollout; it does not bypass approval requirements or task execution.
-
Update Project Webhook events. Please review the documentation for the current list of supported events to ensure your listeners remain compatible.
- Improve permission guards and access control:
- Stop hiding UI elements when users lack permissions and show a no permission alert instead. Allow users with
bb.issues.createpermission to request Project roles directly from the UI. - Allow Project Owners to disable the self-service role request workflow in Project Settings.
- Introduce more granular permission management:
- Add new policy permissions:
bb.policies.getMaskingRulePolicybb.policies.updateMaskingRulePolicy- Add new settings permissions:
bb.settings.getEnvironmentbb.settings.setEnvironmentbb.settings.getWorkspaceProfilebb.settings.setWorkspaceProfile- Permission assignments are updated accordingly:
- The Workspace Admin and DBA receive all these new permissions.
- The Project Owner receives the new policy permissions.
- The Workspace Member receives
bb.settings.getEnvironmentandbb.settings.getWorkspaceProfile.
- Tighten Workspace Members permissions:
- Revoke
bb.settings.get,bb.settings.list,bb.projects.list. - If Workspace Members should not access the user list, create a custom role and revoke
bb.users.listandbb.users.get.
- Revoke
- Redesign the Database Changelog and Revision pages.
- Remove Schema Drift Detection feature:
- Remove
driftedfield fromDatabase messageinv1/database_service.proto. - Remove
driftedfilter option fromListDatabasesAPI (previously supporteddrifted == truefilter). - Remove
dump_versionfield fromChangelogPayloadin store proto. - Update core APIs
CreateSheet,CreatePlan,CreateRollout, andCreateRelease, please refer to the latest API documentation for updated request/response definitions. - Remove
auto_resolve_issueandallow_modify_statementfrom Project Settings. - Remove
maximum_connectionsfrom Instance Settings and useParallel tasks per rolloutin Project Settings instead. - Unify
TRUNCATE_TABLEandTRUNCATEinto a singleTRUNCATEstatement type for Custom Approval CEL expressions. - Update Terraform provider:
- Remove
allow_modify_statementandauto_resolve_issuefrom the project resource. - Remove
auto_resolve_issuefrom the workspace_profile setting resource. - Remove
maximum_connectionsfrom the instance resource. - The
notification_typesin the project webhook are changed toISSUE_CREATED,ISSUE_APPROVAL_REQUESTED,ISSUE_SENT_BACK,PIPELINE_FAILEDandPIPELINE_COMPLETED. - Support configure
allow_request_role,data_classification_config_id,enforce_sql_review,force_issue_labels,issue_labels,labels,require_issue_approval,require_plan_check_no_errorfor the project resource.
π Features
- Add refresh token support (previously only access tokens were supported).
- Allow configuring Access token duration and Refresh token duration (previously the sign-in frequency setting).
- Allow setting
No approval requiredin approval rules when configured conditions are met. - Support Workload Identity with GitLab.
π Enhancements
- Add list sorting for projects, instances, and databases.
- Grant Exemption supports CEL expressions and includes a database selector.
- PostgreSQL - Support ENUM value additions via
ALTER TYPE ... ADD VALUEin schema sync. - MySQL - Prettify generated DDL statements.
π Bug Fixes
- Fix AI setting cache modification issues.
- PostgreSQL β Fix cyclic foreign key dependency handling in schema diff.
- TiDB β Fix DML dry run handling for BATCH syntax.
- PostgreSQL β Fix using identifiers as SELECT target field aliases.
- Oracle β Fix SQL Review incorrectly flagging GRANT / REVOKE as reserved keywords.
https://github.com/bytebase/bytebase/compare/3.13.1...3.14.0
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.