🔔 Notable Changes

• Unified Plan lifecycle view — the Plan detail page shows the full lifecycle of a database change, giving developers one place to follow a change from draft to deployment.

  • The three phases of a database change — change, review, deploy — are shown in sections, allowing developers to edit change, view approval result, and execute deployment in this single page.
  • Issue page is now dedicated primarily for review and approval. Developers will need to go to the plan page to edit changes and create a rollout when needed.

• API breaking changes — Worksheet API moves to project scope (/v1/projects/{id}/worksheets), ListDatabases now requires workspace ID (/v1/workspaces/{id}/databases), branding_logo moves from workspace profile setting to workspace message, GRANT_REQUEST issue type renamed to ROLE_GRANT, UpdateSubscription API deprecated in favor of UploadLicense, and classification description and level description fields removed with level type changed from string to number. See Change Details.

• CEL filter syntax change — Substring-search filters now use contains() instead of matches() across plan, database, instance, project, group, user, service account, workload identity, query history, access grant, and database metadata table filters. See Change Details.

• Read-only data source consolidation — Each instance now allows at most one read-only data source. If more than one is configured, only the first is kept after migration; extra read-only data sources are removed.

• Remove Pro plan 20-user seat cap — Pro plan no longer has a user limit.

• Terraform provider — Updated for 3.17.0 API breaking changes. Supports get, create, update, and list identity providers. See Migration Guide.

🚀 Features

• High Availability (HA) — Support licensed multi-replica deployments backed by a shared external PostgreSQL metadata database. Active replicas are tracked via heartbeats, and background runners coordinate safely across replicas.

• Page Agent — Add an in-app AI assistant with tool-calling, threaded resumable conversations, DOM-aware autocomplete, and token usage tracking.

• Issue Approved webhook event — Support a new webhook event type for issue approval, with redesigned Slack message format.

• MCP query_database tool — Add a new MCP tool for executing SQL queries against managed databases with automatic database resolution.

• CosmosDB — Support local emulator connection and dynamic data masking for all 13 query feature areas.

🎄 Enhancements

• Support executing stored procedures (CALL / EXEC) in SQL Editor by classifying stored procedure execution as DML.

• Support issue type filter in advanced search (Database Change, Role Grant, Database Export, Access Grant).

• Replace data classification file upload with an inline JSON editor and enhance the data classification editor.

• Support masking exemption by classification level, and redesign masking exemption list page.

• Redesign data export creation UI.

• Migrate the frontend from Vue to React across all major pages including settings, projects, databases, instances, plans, issues, and audit logs.

• Upgrade SQL parsing engine for PostgreSQL, MySQL, MongoDB, and CosmosDB from ANTLR to omni parser, improving SQL syntax coverage, consistency across SQL review / schema diff / auto-completion, and error message quality.

• Add configurable --timeout flag for bytebase-action for large SQL checks.

• Expose --enable-json-logging flag in the Helm chart for structured log output.

🐞 Bug Fixes

• Fix false schema diff noise caused by PostgreSQL trigger ordering and CRLF / whitespace normalization.

• Fix SQL editor metadata sync retry flood.

• Fix OAuth discovery to return usable URLs in self-hosted mode.

• Fix stale debounced query reverts in advanced search.

• Fix gh-ost directives in migration-based GitOps workflow.

• PostgreSQL — Fix CRLF line endings causing query truncation in SQL splitter, schema load failure by excluding aggregates from function sync, array subscript handling in column reference normalization, whitespace between LIMIT and FOR UPDATE clause, and nested SELECTs in wrapper statements and CTEs for SQL review.

• MySQL — Fix unqualified SET columns in prior backup for UPDATE JOIN, missing multiStatements param in IAM auth DSN, and role sync for anonymous users.

• TiDB — Remove non-transaction statement handling.

• Oracle — Strip trailing null bytes from schema definitions.

📃 Change Details

API Breaking Changes

1. Worksheet API moves to project scope:

2. APIs that no longer accept workspaces/- (must use workspaces/{id}):

3. Other breaking changes:

CEL Filter Syntax Change

Substring-search CEL filters now use contains() instead of matches(). Existing clients that send filters such as title.matches("..."), name.matches("..."), resource_id.matches("..."), email.matches("..."), host.matches("..."), port.matches("..."), statement.matches("..."), query.matches("..."), or table.matches("...") must switch to the corresponding contains() form.

This applies to plan, database, instance, project, group, user, service account, workload identity, query history, access grant, and database metadata table filters.

3.16.1...3.17.0

Before upgrading: 1) Back up the metadata — in-place downgrade is not supported. 2) Do not run multiple containers on the same data directory. 3) Terraform users: upgrade Bytebase server first, then apply the new Terraform config.

🎄 Enhancements

• Change issue approval status label from "Done" to "Approved" for clarity.

• Add fast-follow refresh mode so rollout status updates more quickly after user actions.

• CosmosDB — Support more query syntax in SQL editor.

🐞 Bug Fixes

• Fix internal error after login caused by InputOtp null check regression.

• Fix popover dismissing when interacting with label selector during plan/issue creation.

• Fix invalid issue type filter in Export Center.

• Fix webhook detail page broken by UUID resource_id migration.

• Harden 3.16 upgrade migration scripts to be idempotent and handle edge cases.

• PostgreSQL — Fix schema dump incorrectly including pg_bitmapindex system schema.

3.16.0...3.16.1

Before upgrading: 1) Back up the metadata — in-place downgrade is not supported. 2) Do not run multiple containers on the same data directory. 3) Terraform users: upgrade Bytebase server first, then apply the new Terraform config.

🔔 Notable Changes

• Workspace API breaking changes - Policy API: /v1/policies → /v1/workspaces/{id}/policies. All workspace-scoped APIs now require explicit workspace ID instead of /v1/workspaces/-. See change details at the bottom.

• User API breaking changes - Decouple identity types and migrate Service Accounts and Workload Identities into separate data models. The unified User API no longer handles these identity types; User.user_type and UserType enum are removed. See change details at the bottom.

• Legacy service account email migration - Legacy emails with {name}@service.bytebase.com and {name}@{project}.service.bytebase.com are auto-migrated. Use the dedicated Service Account and Workload Identity services introduced in 3.15.0.

• Resource ID migration - Several API resource IDs migrate from sequential integers to opaque UUID strings (revision, changelog, issue comment, project webhook). Previously bookmarked integer IDs will no longer work. See change details at the bottom.

• Non-release database migrations now run in parallel; only release-based migrations remain sequential per database.

• Terraform provider 3.16.1 required - Covers workspace policy API changes, UserType removal, resource ID migration, and JIT approval flow. See Migration Guide

🚀 Features

• Just-In-Time (JIT) Data Access - Users without database access can request approval to execute a specific read-only query. Enable JIT in project settings and configure approval rules with the new REQUEST_ACCESS source type. Once approved, the grant is scoped to that query and auto-expires after the configured duration.

• Add GitOps landing page with guided setup for workload identity selection and CI/CD YAML generation.

• Elasticsearch & MongoDB - Support dynamic data masking. Masking is configured per-collection through the Catalog using objectSchema (not the column-based configuration used by relational databases). Global masking rules and masking exemption are not supported for document databases at this time.

🎄 Enhancements

• Redesign issue list with streamlined layout and improved information density. Support sorting by created/updated time, all approval status options (Checking, Pending, Approved, Rejected, Skipped) in advanced search filter, and more prominent approval status in issue detail.

• Standardize timestamp display to relative time with absolute time tooltip.

• Redesign Create Instance page as a full-page layout.

• Support access-token authentication for Bytebase Action, enabling CI/CD pipelines to authenticate to Bytebase via workload identity federation.

• Add pre-execution drift validation that detects schema changes before executing stale tasks.

• Support copying the entire query result in SQL Editor.

• Update default AI model placeholders to current-generation models (GPT-4o, Gemini 2.5 Flash, Claude Sonnet 4).

• MongoDB & Elasticsearch - Preview query results in document view or table view. Live syntax checking and auto-complete in SQL Editor.

• BigQuery & Spanner - Support Workload Identity Federation credentials for non-GCP hosted Bytebase.

• Oracle - Add ROW STORE COMPRESS syntax support.

• PostgreSQL - Support search_path resolution via current user in schema

• PostgreSQL & Oracle - Improve schema sync accuracy.

🐞 Bug Fixes

• Fix issues incorrectly moved to DONE by migration 3.14/0034.

• Skip databases without environments during task creation.

• Classify CALL/EXEC stored procedure statements as DML to allow execution in SQL Editor.

• MariaDB - Fix SQL review plan check not blocking rollout on ERROR-level violations.

• MSSQL - Fix error messages missing line number when rolling out multiple statements.

• Oracle - Fix UTF-8 encoding issues in comment fields during schema sync.

• TiDB - Fix DROP INDEX IF EXISTS walk-through, CHECK_CONSTRAINTS query compatibility for TiDB < 7.4.0, and SQL export resource extraction.
  3.15.1...3.16.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.

📃 Change Details

Workspace API Breaking Changes

1. Policy API path changes (workspace-level policies only):

Environment, instance, and database-level policy bindings are unchanged.

2. APIs that no longer accept workspaces/- (must use workspaces/{id}):

User API Breaking Changes

Resource ID Migration

Resource IDs in the following API resource names change from sequential integers to UUID strings:

Existing records receive randomly generated UUIDs during migration. Any previously bookmarked or cached integer IDs will stop working.

🎄 Enhancements

• Add SQL Editor Read User role for read-only SQL Editor access (SELECT, EXPLAIN, INFO — no DDL/DML).

• Enforce bb.issues.update permission requirement to edit issues, even for issue creators.

🐞 Bug Fixes

• Fix DDL/DML error modal not showing.

• Fix REST API GetSchemaString endpoint returning parse error.

• Fix SQL Editor double-click-drag word selection in reverse direction.

• PostgreSQL — Fix schema dump losing overloaded functions and missing quotes for CamelCase columns in index/constraint DDL.

3.15.0...3.15.1

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.

🔔 Project-level Service Accounts & Workload Identities

We introduce project-level Service Accounts and Workload Identities in addition to the existing workspace-level scope. This enables project-scoped machine identities to follow least privilege and reduce automation blast radius, while clearly separating machine identities from users and aligning them with the resource hierarchy.

• UI & scope changes

  • Workspace Members page now has separate tabs for Users&Groups, Service Accounts, and Workload Identities.
  • Service accounts and workload identities can now be created at both workspace and project levels, governed by their respective IAM policies.
  • Project-level identities are scoped to a single project to enable isolated automation.
  • The account selector for role assignment now supports users, groups, service accounts, and workload identities. Service accounts and workload identities require entering the full email address.

• Breaking changes (API / Terraform users)

  • Machine identities are managed via dedicated APIs (ServiceAccountService, WorkloadIdentityService) instead of the User API.
  • IAM member prefixes updated:
    user:{email} → serviceAccount:{email} / workloadIdentity:{email}
  • Workspace-level Service Account and Workload Identity APIs now require explicit parent workspaces/- instead of an empty string.
    Affected APIs: CreateServiceAccount, ListServiceAccounts, CreateWorkloadIdentity, ListWorkloadIdentities.
    Endpoint change:
    /v1/serviceAccounts → /v1/workspaces/-/serviceAccounts
  • Terraform users must update IAM member prefixes and use the new service account/workload identity resources. Latest provider documentation

🔔 Other Notable Changes

• DDL and DML execution control update

  • Environment condition is added to bb.sql.ddl and bb.sql.dml role grants as a replacement for the disallow_ddl and disallow_dml environment policy. The environment condition is only available when granting roles at the project level for a specific project. Roles granted at the workspace level (which apply to all projects) do not have the environment condition option.
  • Each project-level IAM Policy (i.e. role grant) has a single environment condition that applies to both bb.sql.ddl and bb.sql.dml permissions together. This means you cannot allow DDL but disallow DML (or vice versa) within the same role. If you need different environment restrictions for DDL and DML, the recommended practice is to create 2 separate roles — one with bb.sql.ddl and one with bb.sql.dml — each with its own environment condition.
  • disallow_ddl and disallow_dml are automatically migrated to be reflected in role grants in an OR manner — if for a specific environment, either disallow_ddl or disallow_dml is set to OFF, this environment condition will be configured for the role with bb.sql.ddl or bb.sql.dml permission. This could lead to breaking changes to DDL and DML control if your disallow_ddl and disallow_dml settings differ across environment policies. Please review after upgrading and follow the recommended practice to configure your role grants.
  • Add bb.sql.ddl and bb.sql.dml permissions to the SQL Editor User and Project Owner role.
  • For Terraform users, update the environment policy and your role grants accordingly. Latest provider documentation

• SQL Editor settings consolidation & policy updates

  • Add a dedicated SQL Editor section under Workspace Settings > General, consolidating data export, data copying, admin data source access, max result size, max result rows, and max query time.
  • Max result rows can also be configured at the project level.
  • DataSourceQueryPolicy is merged into QueryDataPolicy and deprecated (auto-migrated).
  • For Terraform users, update bytebase_policy configuration. Latest provider documentation

• Role & permission adjustments

  • Add bb.taskRuns.create permission to the Project Owner role.
  • Remove bb.rollouts.create permission from the Project Developer role (use Project Releaser or Project Owner).
  • Allow managing project IAM policy without the Project Owner role.

• Online migration configuration change

  • Move gh-ost configuration from Plan spec to SQL directive in sheet content (-- gh-ost = { ... }).
  • Remove enable_ghost and ghost_flags from ChangeDatabaseConfig in the Plan API.

• Execution & validation improvements

  • Skip DML dry-run checks when DDL statements are present to reduce false positives. Primarily applied to SQL Review rule Validate the executability of DML statements.

• Cleanup & removals

  • Remove the Archived page (archived projects and instances now appear directly in the dashboard).
  • Remove auto_enable_backup and skip_backup_errors from project settings.
  • Deprecate the legacy issue page and route.

🚀 Features

• MongoDB

  • Use native driver for queries by default, with fallback to mongosh.
  • SQL Editor now supports auto-complete, current statement highlighting, and syntax checking.
  • Support statement-type access control in SQL Editor, allowing administrators to control Read and Write permissions.

• Elasticsearch

  • Support statement-type access control in SQL Editor, allowing administrators to control Read and Write permissions.

🎄 Enhancements

• SQL Editor query results support multi-select via Cmd/Ctrl + Click for rows and columns. Copied data now includes column names.
• Improve the SQL Editor database connection panel layout.
• Normalize Unicode emails to prevent creating accounts with visually identical but technically different addresses.

🐞 Bug Fixes

• Fix access token refresh on SQL Editor LSP websocket reconnection.
• Fix incorrect Learn More link for online migration.
• Google Cloud SQL - Fix IAM authentication while creating instances in Bytebase Cloud.
• PostgreSQL - Support Common Table Expressions (CTE) in backup statement execution.

3.14.1...3.15.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.

🎄 Enhancements

• Improve result masking performance for queries spanning multiple databases, and enhance masking coverage.
• Show rollout link whenever plan has a rollout, regardless of issue status.
• Google Cloud SQL — Support IAM authentication for connections.
• Azure SCIM — Enhance SCIM PATCH API and fix SCIM sync issues.

🐞 Bug Fixes

• Fix database group SQL checks bypassed issue.
• Fix export data issues: add task actions (Run/Retry, Skip, Cancel) and fix skip/download functionality.
• Fix page table showing errors from corrupted localStorage page size.
• Fix minor issues for IM integration: direct messaging not working for new installation and settings page not showing configured data.
• Fix missing users and approvers in some webhook notifications.
• Fix nested transaction patterns that could cause deadlocks under high concurrency.

3.14.0...3.14.1

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.

🔔 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.create permission is added to project releaser role. All custom roles for rollout initiation are advised to be assigned bb.rollouts.create permission. 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.create permission 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.getMaskingRulePolicy
      • bb.policies.updateMaskingRulePolicy
      • bb.policies.createMaskingRulePolicy
      • bb.policies.deleteMaskingRulePolicy
      • bb.policies.getMaskingExemptionPolicy
      • bb.policies.updateMaskingExemptionPolicy
      • bb.policies.createMaskingExemptionPolicy
      • bb.policies.deleteMaskingExemptionPolicy
    • Add new settings permissions:
      • bb.settings.getEnvironment
      • bb.settings.setEnvironment
      • bb.settings.getWorkspaceProfile
      • bb.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.getEnvironment and bb.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.list and bb.users.get.

• Redesign the Database Changelog and Revision pages.

• Remove Schema Drift Detection feature:

  • Remove drifted field from Database message in v1/database_service.proto.
  • Remove drifted filter option from ListDatabases API (previously supported drifted == true filter).
  • Remove dump_version field from ChangelogPayload in store proto.

• Update core APIs CreateSheet, CreatePlan, CreateRollout, and CreateRelease, please refer to the latest API documentation for updated request/response definitions.

• Remove auto_resolve_issue and allow_modify_statement from Project Settings.

• Remove maximum_connections from Instance Settings and use Parallel tasks per rollout in Project Settings instead.

• Unify TRUNCATE_TABLE and TRUNCATE into a single TRUNCATE statement type for Custom Approval CEL expressions.

• Update Terraform provider:

  • Remove allow_modify_statement and auto_resolve_issue from the project resource.
  • Remove auto_resolve_issue from the workspace_profile setting resource.
  • Remove maximum_connections from the instance resource.
  • The notification_types in the project webhook are changed to ISSUE_CREATED, ISSUE_APPROVAL_REQUESTED, ISSUE_SENT_BACK, PIPELINE_FAILED and PIPELINE_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_error for the project resource.

• Releases are now identified by release_id (e.g., my-release-RC00) with automatic train/RC iteration numbering. The title, digest fields are removed from the Release API, and UpdateRelease returns UNIMPLEMENTED. For Terraform, update bytebase_release resource if using title or digest fields.

🚀 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 required in 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 VALUE in 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.

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.

🎄 Enhancements

• Update SQL review template configuration.

🐞 Bug Fixes

• Fix issue label selector missing in new CI/CD layout.
• Fix rollout date filter not working.
• Fix SQL Editor horizontal scroll shortcut.
• Fix SQL review showing incorrect line numbers for multi-statement SQL.

3.13.0...3.13.1

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.

🔔 Notable Changes

• 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. 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.
• 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.
• Remove Schema Template functionality.

🚀 Features

• Support MCP integration.
• Add Workload Identity as a dedicated account type for OIDC-based authentication, with GitHub Actions support.
• Support direct messages for Microsoft Teams.

🎄 Enhancements

• Improve the rollout page with a timeline view, auto-expanded task details, and collapsible task run logs with auto-refresh.
• Allow filtering in SQL Editor results to quickly locate rows.
• Allow selecting a database group to query from in the SQL Editor.
• Snowflake - Support passphrase-protected private keys.
• PostgreSQL - Add event trigger sync and SDL support.
• Trino - Support TLS/SSL.
• Doris - Improve SQL parser compatibility.

3.12.2...3.13.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.

🎄 Enhancements

• Enhance database and query permission checks.
• Improve selector performance with lazy loading for large workspaces.
• SQL Server - Add visualized EXPLAIN support in SQL Editor.
• Doris - Improve syntax compatibility.

🐞 Bug Fixes

• Prevent DML statements from being incorrectly wrapped in CTEs in SQL Editor.
• Fix popup handling for database change statements in SQL Editor.
• Improve and isolate SQL Editor state management across browser tabs.
• Format Cassandra, Spanner, and ClickHouse result data instead of showing raw protobuf.

3.12.1...3.12.2

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.