bytebase

No entries match these filters. Clear filters

1. 1.0.0 Oct 30, 2026 · issue 125

   API surface changed: +1 endpoint, 18 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: +1 endpoint, 18 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • + POST /v1/databases:search
   • ~ GET /v1/projects: response schema changed
   • ~ GET /v1/projects/{project}: response schema changed
   • ~ GET /v1/projects/{project}/accessGrants: response schema changed
   • ~ GET /v1/projects/{project}/accessGrants/{accessGrant}: response schema changed
   • ~ GET /v1/projects:batchGet: response schema changed
   • ~ PATCH /v1/projects/{project}: response schema changed
   • ~ PATCH /v1/projects/{project}/webhooks/{webhook}:updateWebhook: response schema changed
   • ~ POST /v1/instances/{instance}/databases/{database}:export: request body changed; response schema changed
   • ~ POST /v1/projects: response schema changed
   • ~ POST /v1/projects/{project}/accessGrants: response schema changed
   • ~ POST /v1/projects/{project}/accessGrants/{accessGrant}:activate: response schema changed
   • ~ POST /v1/projects/{project}/accessGrants/{accessGrant}:revoke: response schema changed
   • ~ POST /v1/projects/{project}/accessGrants:searchMy: response schema changed
   • ~ POST /v1/projects/{project}/instances/{instance}/databases/{database}:export: request body changed; response schema changed
   • ~ POST /v1/projects/{project}/webhooks/{webhook}:removeWebhook: response schema changed
   • ~ POST /v1/projects/{project}:addWebhook: response schema changed
   • ~ POST /v1/projects/{project}:undelete: response schema changed
   • ~ POST /v1/projects:search: response schema changed
   • New endpoint POST /v1/databases:search⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   1 detail in Everything

2. 3.24.0 Oct 22, 2026 · issue 117

   MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. read-write agents can now manage access requests end-to-end; self-hosted admin recovery runs without downtime; ListPlans gains release and task-status filters.

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch 3.24.0 https://github.com/bytebase/bytebase.git
   # already have the repo? check out this version:
   $ git checkout 3.24.0

   • Extends MCP read-write mode so a connected agent can request just-in-time access, approve or reject issues and access requests, toggle project just-in-time access, grant or revoke masking exemptions, and revoke access grants — all bounded by the signed-in user's own permissions.
   • Adds self-hosted admin recovery: re-enable password sign-in or reset a user's password while Bytebase keeps running, with no restart required, scriptable for unattended use.
   • Adds release and has_release filter parameters to ListPlans API, plus task_status filter, so GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. plans can be distinguished from console-created plans.
   • Adds TLS enforcement for SQL Server and Oracle connections: Verify server certificate now checks the certificate chain and host name, and Oracle TLS connects over TCPS without a wallet.
   • Adds a 10-second connect timeout for Oracle connections, with CONNECTION TIMEOUT available under Extra Parameters to override (use 0 for no limit).

   +1 more show less

   • Adds a setup wizard for new workspaces, guiding through naming, project creation with a sample or real database, and team setup.

   6 details in Everything

   • New supported platform BigQuery SQL review
   └──▷ BREAKING ON UPGRADE

   • !HA mode: stop every replica before starting 3.24.0 — rolling upgrades are not supported. A replica still on an older version saves access grants that 3.24.0 cannot match, and those grants stop working for queries and exports.
   • !SQL Server: verify_tls_certificate = true on a data source is turned off during upgrade; re-enable it via Terraform only after confirming the certificate verifies.
   • !Oracle: use_ssl = true on a data source is turned off during upgrade, and stored CA and client certificates are removed; re-enable via Terraform only after confirming the port serves TCPS.
3. 1.0.0 Oct 17, 2026 · issue 111

   API surface changed: +1 endpoint, 2 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: +1 endpoint, 2 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • + GET /v1/projects/{project}/issues/{issue}/reviewRuns/{reviewRun}
   • ~ GET /v1/actuator/info: response schema changed
   • ~ POST /v1/ai/chat: response schema changed
   • New endpoint GET /v1/projects/{project}/issues/{issue}/reviewRuns/{reviewRun}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   1 detail in Everything

4. 1.0.0 Oct 13, 2026 · issue 107

   API surface changed: 4 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: 4 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • ~ GET /v1/actuator/info: response schema changed
   • ~ POST /bytebase.v1.SQLService/GetQueryHistory: param Connect-Protocol-Version (header) now optional
   • ~ POST /bytebase.v1.SQLService/ListQueryHistories: param Connect-Protocol-Version (header) now optional
   • ~ POST /bytebase.v1.SQLService/SearchQueryHistories: param Connect-Protocol-Version (header) now optional
   • POST /bytebase.v1.SQLService/GetQueryHistory: param Connect-Protocol-Version (header) now optional⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • POST /bytebase.v1.SQLService/ListQueryHistories: param Connect-Protocol-Version (header) now optional
   • POST /bytebase.v1.SQLService/SearchQueryHistories: param Connect-Protocol-Version (header) now optional

   3 details in Everything

5. 3.23.0 Sep 24, 2026 · issue 085

   Bytebase 3.23.0 adds MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. access policies, inline plan-review comments, any-OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. workload identitiesworkload identitiesAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials., and a query-plan visualizer in SQL Editor.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch 3.23.0 https://github.com/bytebase/bytebase.git
   # already have the repo? check out this version:
   $ git checkout 3.23.0

   └──▷ USE IT
   Authenticate the Terraform provider as a workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. (e.g. from GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure.) instead of a long-lived service account key.
   hcl copy

   provider "bytebase" {
     url                          = "https://bytebase.example.com"
     workload_identity_email      = "ci-deployer@bytebase.example.com"
     workload_identity_token_file = "/var/run/secrets/bytebase/token"
   }

   Register any OIDC provider (e.g. HashiCorp Vault, Azure AD) as a Bytebase workload identity when the issuer does not publish a standard discovery document.
   hcl copy

   resource "bytebase_workload_identity" "vault" {
     name              = "vault-ci"
     issuer_url        = "https://vault.example.com/v1/identity/oidc"
     jwks_url          = "https://vault.example.com/v1/identity/oidc/.well-known/keys"
     allowed_audiences = ["bytebase"]
     subject_pattern   = "my-org/my-repo"
     provider_type     = "OIDC"
   }

   Query the new MCP settings endpoint (requires authentication) after removing the now-deleted GET /v1/mcp/info call.
   copy

   $ curl -H 'Authorization: Bearer <token>' \
     https://bytebase.example.com/v1/actuator/info \
     | jq '.mcpSetting'

   • Adds workload_identity_email, workload_identity_token, and workload_identity_token_file provider fields so the Terraform provider can authenticate as a workload identity instead of a service account key.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds provider_type = "OIDC" and optional jwks_url to bytebase_workload_identity in the Terraform provider, enabling any OIDC issuer as a workload identity.
   • Adds GET /v1/actuator/info (ActuatorService.GetActuatorInfo) as the new source for MCP settings, replacing the removed GET /v1/mcp/info.
   • Renames the audit-log user field to actor in the API and exports, with values now typed as users/{email}, serviceAccounts/{email}, or workloadIdentities/{email}.
   • Replaces mssql_explain_format with explain_format in the query API for the inline query-plan visualizer.

   +12 more show less

   • Adds MCP access policy control under Integration > MCP > Access policy with three levels: Disabled, Read-only, and Read-write; applies to already-connected clients immediately.
   • Adds inline comments on specific SQL lines in the Plan detail editor, with thread replies, Resolve/Reopen actions, an open-thread counter, and thread navigation.
   • Supports any OIDC issuer for workload identities, with an optional JWKSJWKSA JSON Web Key Set, a published collection of cryptographic keys. Applications use it to find the public key needed to verify a token's signature. URL for issuers that do not publish a discovery document.
   • Adds audit-log recording of requests refused by permission checks or blocked by the MCP access policy, written as WARNING; enables stdout logging of every refusal when Enable audit logging to stdout is on (self-hosted).
   • Adds a query-plan visualizer in the SQL Editor result pane (text, diagram, grid, or summary) for PostgreSQL, SQL Server, and Spanner, including EXPLAIN FORMAT JSON, XML, YAML, and ANALYZE on PostgreSQL.
   • Adds project setting Allow approval by the person who last changed the plan to prevent the last plan editor from approving their own change.
   • Adds bytebase.podAnnotations Helm value to set pod annotations on the Bytebase pod (self-hosted), for example for Prometheus scraping.
   • Adds Skip metadata lock check opt-in option to MySQL gh-ost migrations.
   • Requires DML permission (bb.sql.select alone is no longer sufficient) for data-modifying PostgreSQL queries in SQL Editor, including SELECT with a data-modifying WITH clause and EXPLAIN ANALYZE of a write.
   • Requires access to the linked database for Oracle database link queries (schema.table@link) in SQL Editor, export, or MCP; links to unmanaged or external instances are refused before the query runs.
   • Enables statement.sql_type approval rules and risk levels for OceanBase changes.
   • Adds SQL Editor AI assistant chat history (last 20 conversations per workspace and user) with inline-editable conversation titles.
   • Adds workload_identity_email, workload_identity_token, and workload_identity_token_file provider fields so the Terraform provider can authenticate as a workload identity instead of a service account key.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds GET /v1/actuator/info (ActuatorService.GetActuatorInfo) as the new source for MCP settings, replacing the removed GET /v1/mcp/info.
   • Adds MCP access policy control under Integration > MCP > Access policy with three levels: Disabled, Read-only, and Read-write; applies to already-connected clients immediately.
   • Adds inline comments on specific SQL lines in the Plan detail editor, with thread replies, Resolve/Reopen actions, an open-thread counter, and thread navigation.
   • Adds a query-plan visualizer in the SQL Editor result pane (text, diagram, grid, or summary) for PostgreSQL, SQL Server, and Spanner, including EXPLAIN FORMAT JSON, XML, YAML, and ANALYZE on PostgreSQL.

   +3 more show less

   • Adds project setting Allow approval by the person who last changed the plan to prevent the last plan editor from approving their own change.
   • Adds bytebase.podAnnotations Helm value to set pod annotations on the Bytebase pod (self-hosted), for example for Prometheus scraping.
   • Adds Skip metadata lock check opt-in option to MySQL gh-ost migrations.

   9 more in Everything

   └──▷ BREAKING ON UPGRADE

   • !GET /v1/mcp/info (WorkspaceService.GetMCPInfo) is removed; read mcpSetting from GET /v1/actuator/info (ActuatorService.GetActuatorInfo) instead. The modes, methods, engines, and data_masking_available fields have no replacement.
   • !The audit-log user field is renamed actor in the API and exports; update filters from user == 'users/bb@bytebase.com' to actor == 'users/bb@bytebase.com'.
   • !mssql_explain_format is renamed explain_format in the query API; integrations using the old field name will break.
   • !bytebase_workload_identity in the Terraform provider now requires issuer_url, allowed_audiences, and subject_pattern; existing resources missing these fields will fail to apply.
   • !Existing GitHub and GitLab workload identities whose subject pattern matches every repository or project (e.g. *, repo:*, project_path:*) stop authenticating until narrowed to at least the owner or group.
   • !Workload identity pipelines requesting an audience not on the identity's allowed list stop authenticating; the audience must be added to the list or the pipeline must request an allowed audience.
   • !New workspaces default to MCP access policy Read-only; workspaces that have never set a policy remain Read-write until an admin explicitly sets one.
   • !MCP clients connected before 3.22.0 cannot refresh their tokens and will fail with invalid_grant once the current access tokenaccess tokenA credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. expires; the server must be removed and re-added in each client.
   • !PostgreSQL queries in SQL Editor that use a data-modifying WITH clause or EXPLAIN ANALYZE on a write now require DML permission; bb.sql.select alone is no longer sufficient.
   • !Oracle database link queries (schema.table@link) now require the same grant as querying the linked database directly; links to unmanaged or external instances are refused.
   • !Service accounts can no longer sign in to the Bytebase web console.
   • !ListTaskRuns is now paginated; callers that assumed a single full response must be updated to page through results.
   • !The four BatchGet API methods are now all-or-nothing; a request that partially fails now returns an error instead of partial results.
   • !Update API methods now reject requests whose body disagrees with update_mask.
   • !The login-page restriction endpoint is renamed; callers using the old name will break.
   • !Listing identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. now requires authentication; unauthenticated calls will be rejected.
6. 1.0.0 Sep 23, 2026 · issue 083

   bytebase now publishes an API — 278 endpoints across 33 areas: Databaseservice, Instanceservice, Userservice, …⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • Databaseservice (31 endpoints) — DatabaseService manages databases and their schemas.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Instanceservice (27 endpoints) — InstanceService manages database instances and their connections.
   • Userservice (16 endpoints) — UserService manages user accounts and authentication.
   • Orgpolicyservice (15 endpoints) — OrgPolicyService manages organizational policies at various resource levels.
   • Projectservice (15 endpoints) — ProjectService manages projects that group databases and changes.

   +4 more show less

   • Issueservice (14 endpoints) — IssueService manages issues for tracking database changes and tasks.
   • Authservice (11 endpoints) — AuthService handles user authentication operations.
   • Rolloutservice (11 endpoints) — RolloutService manages the execution of deployment plans.
   • 25 more areas: Savedqueryservice, Subscriptionservice, Releaseservice, Revisionservice, Sqlservice, Serviceaccountservice, Workloadidentityservice, Workspaceservice, Identityproviderservice, Planservice, Accessgrantservice, Groupservice, Databasegroupservice, Reviewconfigservice, Roleservice, Auditlogservice, Changelogservice, Databasecatalogservice, Settingservice, Queryhistoryservice, Sheetservice, Celservice, Instanceroleservice, Aiservice, Actuatorservice

   9 details in Everything

7. 3.22.1 Sep 10, 2026 · issue 083

   Bytebase 3.22.1 adds GPT-5 model support and improves service account search in Grant Access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch 3.22.1 https://github.com/bytebase/bytebase.git
   # already have the repo? check out this version:
   $ git checkout 3.22.1

   • Supports GPT-5 models for AI features alongside existing GPT-4o support.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   1 detail in Everything

8. 3.22.0 Aug 28, 2026 · issue 083

   Bytebase 3.22.0 adds project-scoped instances, Data Explorer, login lockout, new bytebase recovery CLI, and per-object saved-query sharing.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch 3.22.0 https://github.com/bytebase/bytebase.git
   # already have the repo? check out this version:
   $ git checkout 3.22.0

   └──▷ TRY IT
   Recover a locked-out admin by re-enabling password sign-in directly against the metadata database when the UI is inaccessible.
   copy

   $ bytebase recovery

   Allow a remote Prometheus scraper to reach /metrics when Bytebase sits behind a gateway or NetworkPolicyNetworkPolicyA Kubernetes API object that defines which pods may send or receive traffic, enforced by the cluster's CNI plugin to give cyber tools namespace-level network segmentation without host firewall rules..
   copy

   $ bytebase --metrics-remote-access

   • Adds bytebase recovery CLI command as a break-glass path to re-enable password sign-in or reset a user's password directly against the metadata database, bypassing the UI.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Restricts /metrics to loopback-only by default; adds --metrics-remote-access startup flag to restore remote scraper access when the endpoint is protected by a gateway, firewall, or NetworkPolicy.
   • Requires authentication on /v1/actuator/info; monitoring scripts that poll this endpoint must now include a credential.
   • Renames WorksheetService to SavedQueryService with new REST paths /v1/{parent=projects/*}/savedQueries… and …/savedQueryFolders…; per-object IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. replaces the visibility field.
   • Replaces bb.worksheets.* permissions with per-verb bb.savedQueries.{create, search, list, get, getIamPolicy, setIamPolicy, update, delete} permissions on custom roles.

   +6 more show less

   • Adds project-scoped instances: instances can now be assigned to a single project via an optional parent argument on the bytebase_instance Terraform resource (provider 3.22.1).
   • Adds Data Explorer to SQL Editor for browsing table and collection data without writing a query, with native predicate filtering per engine (WHERE for SQL, filter document for MongoDB, query expression for Elasticsearch).
   • Enforces disallow_password_signin and enforce_identity_domain uniformly for all accounts including workspace admins.
   • Adds login attempt lockout: repeated failed sign-in attempts for password, emailed code, or MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. code lock the targeted credential for a cooldown period.
   • Adds operational health metrics to /metrics: schema sync health, runner cycles, license expiry, and instance capacity.
   • Adds per-object sharing for Saved Queries: grant Viewer or Editor access to individual user: and group: principals via SetIamPolicy, and organize queries into folders with drag-and-drop and star favorites.
   • Adds bytebase recovery CLI command as a break-glass path to re-enable password sign-in or reset a user's password directly against the metadata database, bypassing the UI.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Renames WorksheetService to SavedQueryService with new REST paths /v1/{parent=projects/*}/savedQueries… and …/savedQueryFolders…; per-object IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. replaces the visibility field.
   • Adds project-scoped instances: instances can now be assigned to a single project via an optional parent argument on the bytebase_instance Terraform resource (provider 3.22.1).
   • Adds Data Explorer to SQL Editor for browsing table and collection data without writing a query, with native predicate filtering per engine (WHERE for SQL, filter document for MongoDB, query expression for Elasticsearch).
   • Adds login attempt lockout: repeated failed sign-in attempts for password, emailed code, or MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. code lock the targeted credential for a cooldown period.

   +1 more show less

   • Adds per-object sharing for Saved Queries: grant Viewer or Editor access to individual user: and group: principals via SetIamPolicy, and organize queries into folders with drag-and-drop and star favorites.

   5 more in Everything

   └──▷ BREAKING ON UPGRADE

   • !WorksheetService is renamed to SavedQueryService with no compatibility aliases — all RPCs, messages, and REST paths (e.g. /v1/{parent=projects/*}/worksheets…) must be updated to their new equivalents.
   • !The visibility field (PRIVATE / PROJECT_READ / PROJECT_WRITE) is removed from saved queries; on upgrade every existing saved query migrates to owner-private and must be re-shared explicitly.
   • !Custom roles referencing bb.worksheets.* permissions must be updated to the new bb.savedQueries.* verb family.
   • !/metrics now only accepts requests from the server host (loopback); remote Prometheus scrapers pointed directly at the server stop collecting on upgrade unless --metrics-remote-access is set.
   • !/v1/actuator/info now requires authentication; unauthenticated monitoring scripts stop working on upgrade.
   • !disallow_password_signin and enforce_identity_domain now apply to workspace admins too — an admin whose only sign-in path is blocked by these settings will be locked out on upgrade.
   • !Terraform provider 3.22.1: the cluster field in data_sources blocks and the computed service_key attribute on bytebase_user are removed — delete any references from Terraform configs.
   • !Terraform provider 3.22.1: project webhook URLs are now write-only; data sources read back an empty webhooks.url.
   • !Two Instance- and Database-level organization-policy API endpoints previously unsupported for project-scoped instances are removed.
   • !Archiving or restoring an instance now returns an error if it has task runs in PENDING, AVAILABLE, or RUNNING state — cancel or wait for those runs before archiving/restoring.
   • !The legacy async export-data issue workflow is fully removed; integrations polling the old export-issue API must migrate to JITJITA runtime compilation strategy where code is translated from an intermediate form to native machine instructions at execution time, giving tools the speed of compiled code without sacrificing dynamic flexibility. access-grant exports or synchronous SQL Editor export.
9. 3.21.1 Aug 13, 2026 · release notes

   Adds DynamoDB per-instance AWS credential configuration including cross-account role ARN and external ID support

   └──▷ GET THIS VERSION

   copy

   $ git clone --branch 3.21.1 https://github.com/bytebase/bytebase.git
   # already have the repo? check out this version:
   $ git checkout 3.21.1

   └──▷ HOW TO FIND IT
   Configure Bytebase to connect to DynamoDB using a specific cross-account IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. role for access control.
   📍Add AWS credentials, cross-account role ARN, and external ID to the instance configuration, then use Test Connection to verify the connection.
10. 3.21.0 Jul 30, 2026 · release notes

    Bytebase 3.21 adds MySQL state-based GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control., label-driven approvals, and list APIs for query histories/workSheets

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.21.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.21.0

    • Adds support for listing worksheets across users/projects via new bb.worksheets.list permission and List API
    • Adds MySQL state-based GitOps workflow (beta) supporting declarative SDL schema management with routines, triggers, and events
    • Allows adding issue labels during plan drafting and referencing them in Custom Approval conditions

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !SearchQueryHistories route changed from POST /v1/queryHistories:search to POST /v1/{parent=projects/*}/queryHistories:search; parent is now required.
    • !InstanceService.GetInstance and ListInstances consumers must read project_id/instance_id instead of parsing host for Spanner/BigQueryBigQueryA serverless, cloud-hosted analytical database from Google that runs SQL queries across massive datasets without managing infrastructure, giving cyber tools scalable storage and fast querying over large volumes of log or event data..
    • !ChangelogService replaces DatabaseService for list/get changelogs; REST paths unchanged but gRPCgRPCAn open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. method names changed.
    • !QueryHistoryService replaces SQLService for query history operations; SearchQueryHistories moved to project scope.
    • !DatabaseService.DiffMetadata replaces anonymous SQLService.DiffMetadata; requires bb.databases.diffMetadata permission and new request shape.
    • !SQLService.AICompletion removed; use AIService.Chat instead.
    • !SQLITE removed from Engine enum.
    • !Instance.sync_databases reshaped from repeated string to SyncDatabases message.
    • !Plan list filter has_issue removed; callers sending it receive InvalidArgument.
11. 3.20.1 Jul 16, 2026 · release notes

    Bytebase 3.20.1 restores workspace setting for Maximum role expiration and improves plan deployment UI

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.20.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.20.1

    • Plan deployment section now shows task execution details inline within the deploy view

    1 detail in Everything

12. 3.20.0 Jul 2, 2026 · release notes

    Bytebase 3.20 adds GCP Cloud SQL IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. auth, Vault token_type support and workspace announcement themes.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.20.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.20.0

    • Adds GCP Cloud SQL IAM authentication for external PostgreSQL metadata database connections on self-hosted deployments via Helm
    • Adds token_type field to HashiCorp Vault integration allowing PLAIN, ENVIRONMENT, or FILE token sources
    • Adds theme configuration for workspace announcements replacing the deprecated level field
    • Binds access request duration to the new maximum_request_expiration_in_seconds workspace setting

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The workspace setting maximum_role_expiration_in_seconds is renamed to maximum_request_expiration_in_seconds
    • !The Terraform field announcement.level under workspace_profile is deprecated and must be replaced with theme (containing background / text)
    • !The approval source EXPORT_DATA is deprecated; remove it from approval-flow configs and use the JITJITA runtime compilation strategy where code is translated from an intermediate form to native machine instructions at execution time, giving tools the speed of compiled code without sacrificing dynamic flexibility. data-export flow instead
    • !Seven SQL review rules (STATEMENT_SELECT_FULL_TABLE_SCAN, STATEMENT_QUERY_MINIMUM_PLAN_LEVEL, STATEMENT_DISALLOW_USING_FILESORT, STATEMENT_DISALLOW_USING_TEMPORARY, STATEMENT_MAXIMUM_JOIN_TABLE_COUNT, STATEMENT_JOIN_STRICT_COLUMN_ATTRS, STATEMENT_MAXIMUM_LIMIT_VALUE) are removed; remove them from review configs
13. 3.19.1 Jun 18, 2026 · release notes

    StarRocks parser support and shareable SQL Editor query history URLs

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.19.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.19.1

    • Adds dedicated StarRocks parser support, enabling query lineage, materialized view syncing, and correct handling of generated columns, async materialized views, INSERT OVERWRITE, and CTE-prefixed DELETE/UPDATE.
    • SQL Editor query history items now have a direct, shareable URL that reopens the exact statement and database connection.

    2 details in Everything

14. 3.19.0 Jun 5, 2026 · release notes

    Bytebase 3.19 adds just-in-time data export approval flows and active VCSVCSVersion control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. user tracking for GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.19.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.19.0

    └──▷ USE IT
    Configure JITJITA runtime compilation strategy where code is translated from an intermediate form to native machine instructions at execution time, giving tools the speed of compiled code without sacrificing dynamic flexibility. data export rules in Terraform to ensure exports go through approval.
    config copy

    # In your Terraform config, add the following rule under REQUEST_ACCESS source:
    rule {
      source = "REQUEST_ACCESS"
      condition = "request.data_export == true"
      # ... other settings
    }

    Verify that your CI/CD pipeline uses a compatible bytebase-action version to avoid failure during database operations.
    copy

    $ # Pin your CI to a specific cloud tag or dated version within the compatibility window
    export BYTEBASE_ACTION_VERSION=cloud

    • Adds just-in-time data export access workflow via the SQL Editor with an approval process and migration of existing rules to the Custom Approval page
    • Adds support for configuring just-in-time data export rules in Terraform using request.data_export == true under the REQUEST_ACCESS source
    • Adds active VCS user tracking for GitOps where non-bot PR/MR authors seen by bytebase-release workflows count toward license limits over a 90-day window, with CSV download from the Subscription page

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !bytebase-action check and bytebase-action rollout now fail with an error (previously a warning) when the action version is outside the compatibility window
15. 3.18.1 Jun 1, 2026 · release notes

    Bytebase 3.18.1 adds PostgreSQL 18 support, MCP OAuthMCP OAuthAn authentication layer for the Model Context Protocol that lets MCP clients obtain delegated access tokens so cyber tools can call MCP servers on a user's behalf without handling raw credentials. for SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally., and removes the --demo flag

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.18.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.18.1

    • Adds support for PostgreSQL 18 with recognition of built-ins like uuidv7() in SQL analysis and schema diff.
    • Enables automatic MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. OAuth flow completion against cloud.bytebase.com for SaaS deployments without manual configuration.
    • Makes non-read-only Query data source use the admin data source when the query data policy allows it.
    • Allows gh-ost migrations to honor the configured data-source SSH tunnel for MySQL connections and binlog reading.
    • Adds APP_IM support to the bytebase_setting Terraform resource in provider 3.18.1.

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The --demo server flag has been removed and will cause startup errors if used.
    • !Terraform provider 3.18.1 marks the webhook URL in settings as write-only.
16. 3.18.0 May 14, 2026 · release notes

    Bytebase 3.18 adds Google Chat webhook, AWS RDS IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. auth, MariaDB DML rollback, and --custom-header CLI flag.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.18.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.18.0

    • require_2fa is renamed to require_mfa; plan_spec_update is replaced by plan_update with a restructured payload; Issue.ApprovalStatus is moved to top-level ApprovalStatus
    • Bytebase Terraform provider 3.18.0 adds write-only sensitive fields and a provider-level custom_header block
    • New API endpoint or method RetryIssueApproval allows retrying issues stuck in CHECKING status
    • Adds support for MariaDB DML rollback using prior-backup, matching MySQL behavior
    • Adds CosmosDB cross-partition query support

    +2 more show less

    • Bytebase Action now accepts the --custom-header flag for header-based access proxies in CI/CD pipelines
    • Adds Google Chat as a project webhook destination

    7 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The require_2fa field on WorkspaceProfileSetting is renamed to require_mfa; callers updating workspace profile settings via SettingService.UpdateSetting must update their config or IaCIaCInfrastructure as Code: the practice of defining and provisioning compute infrastructure through machine-readable config files rather than manual processes, giving cyber tools repeatable, version-controlled environment setup. to use the new name.
    • !IssueComment.plan_spec_update is replaced by plan_update; consumers of IssueService.ListIssueComments or issue activity events must read plan_update.from_specs / to_specs instead of the previous PlanSpecUpdate structure.
    • !The nested enum Issue.ApprovalStatus is removed and moved to top-level bytebase.v1.ApprovalStatus; clients referencing the nested type by name (e.g., generated Go or TS types) must update imports or type references.
17. 3.17.1 Apr 23, 2026 · release notes

    Bytebase 3.17.1 adds instance TLS modes and Oracle/PG/MySQL/MSSQL SQL review rules

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.17.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.17.1

    • Adds Disabled, TLS, and Mutual TLSMutual TLSMutual TLS, an encrypted connection where both client and server present certificates to prove their identity. It helps services verify who they are communicating with. options for instance TLS configuration via configured file path.
    • Adds STATEMENT_DISALLOW_TRUNCATE rule for Oracle, PostgreSQL, MySQL, and MSSQL SQL Review.
    • Extends STATEMENT_WHERE_DISALLOW_FUNCTIONS_AND_CALCULATIONS to Oracle and PostgreSQL; narrows it to flag functions/calculations only on indexed columns.

    3 details in Everything

18. 3.17.0 Apr 9, 2026 · release notes

    Bytebase 3.17.0 adds HA support, Page Agent AI assistant, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. query_database tool, and CosmosDB local emulator.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.17.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.17.0

    • Supports licensed multi-replica deployments with shared external PostgreSQL metadata for High Availability
    • Adds in-app Page Agent with threaded resumable conversations, DOMDOMThe browser's in-memory tree representation of a web page's structure, standardized by the W3C, giving cyber tools a programmable interface to read or manipulate page content at runtime.-aware autocomplete, and tool-callingtool-callingA model's ability to answer with a structured request to run a named function or API, which the application executes and returns. It is how agents take actions.
    • Adds MCP query_database tool for executing SQL queries against managed databases
    • Adds support for CosmosDB local emulator connection and dynamic data masking
    • Adds new Issue Approved webhook event type with redesigned Slack message format

    +4 more show less

    • Supports executing stored procedures (CALL / EXEC) in SQL Editor by classifying them as DML
    • Supports issue type filter in advanced search (Database Change, Role Grant, Database Export, Access Grant)
    • Replaces data classification file upload with an inline JSON editor
    • Exposes --enable-json-logging flag in the Helm chart for structured log output

    9 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !branding_logo moved from workspace profile setting to workspace message (logo field on workspace message)
    • !GRANT_REQUEST issue type renamed to ROLE_GRANT in API requests and responses
    • !UpdateSubscription API deprecated; use UploadLicense (PATCH /v1/subscription/license) instead
    • !Classification level description field removed and level type changed from string to number (int)
    • !Worksheet API scoped to project: /v1/projects/{id}/worksheets replaces global /v1/worksheets
    • !ListDatabases now requires explicit workspace ID (/v1/workspaces/{id}/databases) instead of workspaces/-
    • !CELCELCommon Expression Language, an open-source expression language maintained by Google, used to embed lightweight, safe policy evaluation logic into tools without running a full scripting engine. filter substring-search syntax changed from matches() to contains() across plan, database, instance, project, group, user, service account, workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials., query history, access grant, and database metadata table filters
    • !Each instance now allows at most one read-only data source; extra configured sources are removed after migration
19. 3.16.1 Mar 26, 2026 · release notes

    Bytebase 3.16.1 adds fast-follow refresh mode for rollout status and improved CosmosDB SQL editor query support

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.16.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.16.1

    • Adds fast-follow refresh mode so rollout status updates more quickly after user actions
    • Expands supported query syntax for CosmosDB in the SQL editor

    2 details in Everything

20. 3.16.0 Mar 12, 2026 · release notes

    Bytebase 3.16 adds JITJITA runtime compilation strategy where code is translated from an intermediate form to native machine instructions at execution time, giving tools the speed of compiled code without sacrificing dynamic flexibility. data access approval, GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. landing page, dynamic masking for MongoDB/Elasticsearch, and workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. federation.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.16.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.16.0

    └──▷ HOW TO FIND IT
    Access the new GitOps landing page in the Bytebase UI to generate CI/CD YAML files.
    📍In the Bytebase console, navigate to the new GitOps section and follow the guided setup for workload identity selection.
    • Adds Just-In-Time (JIT) data access feature allowing users to request read-only query approval with REQUEST_ACCESS source type in project settings
    • Adds GitOps landing page with guided setup for workload identity selection and CI/CD YAML generation
    • Adds dynamic data masking support for MongoDB collections via Catalog objectSchema configuration
    • Adds dynamic data masking support for Elasticsearch indices via Catalog objectSchema configuration
    • Adds pre-execution drift validation to detect schema changes before executing stale tasks

    +6 more show less

    • Adds access-token authentication for Bytebase Action enabling CI/CD pipelines to authenticate via workload identity federation
    • Adds preview of query results in document view or table view for MongoDB and Elasticsearch databases
    • Adds live syntax checking and auto-complete in SQL Editor for MongoDB and Elasticsearch databases
    • Adds support for Workload Identity Federation credentials for non-GCP hosted Bytebase with BigQueryBigQueryA serverless, cloud-hosted analytical database from Google that runs SQL queries across massive datasets without managing infrastructure, giving cyber tools scalable storage and fast querying over large volumes of log or event data. & Spanner
    • Adds ROW STORE COMPRESS syntax support for Oracle databases
    • Adds search_path resolution via current user for PostgreSQL databases

    11 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Policy API paths change from /v1/policies to /v1/workspaces/{id}/policies; all workspace-scoped APIs now require explicit workspace ID instead of /v1/workspaces/-
    • !User API User.user_type field and UserType enum are removed; Service Accounts and Workload Identities must use dedicated services
    • !Resource IDs for revisions, changelogs, issue comments, and project webhooks migrate from sequential integers to opaque UUIDUUIDA universally unique identifier, usually a 128-bit value used to identify an object across systems. It is designed to make independently generated identifiers unlikely to collide. strings, invalidating previously bookmarked integer IDs
21. 3.15.1 Feb 26, 2026 · release notes

    Bytebase 3.15.1 adds a dedicated SQL Editor Read User role for SELECT/EXPLAIN/INFO-only access.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.15.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.15.1

    • Enforces bb.issues.update permission requirement when editing issues, removing the implicit creator-can-always-edit exception.

    1 detail in Everything

    └──▷ BREAKING ON UPGRADE

    • !Issue creators who previously could edit their own issues without bb.issues.update will now be denied unless that permission is explicitly granted.
22. 3.15.0 Feb 12, 2026 · release notes

    Bytebase 3.15 introduces project-level service accounts, workload identitiesworkload identitiesAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials., and MongoDB statement-type access control in SQL Editor

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.15.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.15.0

    └──▷ TRY IT
    Create a project-scoped service account using the new dedicated API endpoint
    copy

    $ curl -X POST https://<bytebase-host>/v1/workspaces/-/serviceAccounts \
      -H "Authorization: Bearer <token>" \
      -d '{"name": "projects/my-project/serviceAccounts/ci-bot", "displayName": "CI Bot"}'

    Configure gh-ost online migration directly in the SQL sheet instead of using Plan spec flags
    text copy

    -- gh-ost = {
      "max-lag-millis": 1500,
      "initial-heartbeat-delay": 4
    }
    ALTER TABLE users ADD COLUMN last_login TIMESTAMP;

    • Adds ServiceAccountService and WorkloadIdentityService APIs for managing machine identities at the project level
    • Adds workloadIdentity:{email} IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. member prefix for project-scoped Workload Identities
    • Updates Service Account endpoint from /v1/serviceAccounts to /v1/workspaces/-/serviceAccounts for workspace-level creation and listing
    • Adds statement-type access control in SQL Editor for MongoDB and Elasticsearch data sources
    • Moves gh-ost configuration into SQL directive syntax (-- gh-ost = { ... }) within sheet content

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Machine identities must now use ServiceAccountService or WorkloadIdentityService APIs instead of the User API
    • !IAM member prefix changed from user:{email} to serviceAccount:{email} or workloadIdentity:{email} for machine identities
    • !Workspace-level Service Account and Workload Identity APIs now require explicit parent workspaces/- in the path (e.g. /v1/workspaces/-/serviceAccounts) instead of an empty string
23. 3.14.1 Jan 29, 2026 · release notes

    Bytebase 3.14.1 adds Google Cloud SQL IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. authentication support and improves result masking performance.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.14.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.14.1

    • Adds Google Cloud SQL IAM authentication support for database connections
    • Improves result masking performance for queries spanning multiple databases and enhances masking coverage

    2 details in Everything

24. 3.14.0 Jan 15, 2026 · release notes

    Bytebase v3.14 introduces refresh tokensrefresh tokensA credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API., granular masking/exemption policies, Terraform project settings, and Workload Identity support.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.14.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.14.0

    └──▷ HOW TO FIND IT
    Allow a Project Releaser to manually create rollouts when SQL review fails but the issue is approved.
    📍grant bb.rollouts.create to project releaser
    Grant granular access to manage masking rules, previously lumped into broader admin roles.
    📍grant bb.policies.createMaskingRulePolicy, bb.policies.getMaskingRulePolicy, bb.policies.updateMaskingRulePolicy, bb.policies.deleteMaskingRulePolicy to role Data Privacy Lead
    Configure the Terraform project resource with new SQL review and approval controls.
    hcl copy

    resource "bytebase_project" "main" {
      name        = "production"
      enforce_sql_review = true
      require_issue_approval = true
      data_classification_config_id = var.classification_id
    }

    • Adds bb.rollouts.create permission to control who can initiate a rollout
    • Adds eight new policy permissions for masking rules and exemptions (bb.policies.*MaskingRulePolicy, bb.policies.*MaskingExemptionPolicy)
    • Adds four new settings permissions (bb.settings.getEnvironment, bb.settings.setEnvironment, bb.settings.getWorkspaceProfile, bb.settings.setWorkspaceProfile)
    • Removes drifted field from Database message proto and drifted filter from ListDatabases API, ending Schema Drift Detection
    • Adds support for allow_request_role, data_classification_config_id, enforce_sql_review, force_issue_labels, issue_labels, labels, require_issue_approval, require_plan_check_no_error in the Terraform bytebase_project resource

    +1 more show less

    • Supports Workload Identity authentication with GitLab CI for user groups

    6 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Removes drifted field from Database message in v1/database_service.proto and drifted filter option from ListDatabases API
    • !Removes dump_version field from ChangelogPayload in store proto
    • !Replaces maximum_connections in Instance Settings with Parallel tasks per rollout in Project Settings and removes the old setting
    • !Updates notification_types for project webhooks to ISSUE_CREATED, ISSUE_APPROVAL_REQUESTED, ISSUE_SENT_BACK, PIPELINE_FAILED and PIPELINE_COMPLETED
    • !Releases are now identified by release_id with automatic train/RC iteration numbering; title and digest fields are removed from the Release API
    • !Revokes bb.settings.get, bb.settings.list, bb.projects.list from Workspace Members role
25. 3.13.0 Dec 18, 2025 · release notes

    Bytebase 3.13.0 adds MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. integration, Workload Identity for OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user./GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure., and Microsoft Teams direct messages.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.13.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.13.0

    └──▷ USE IT
    Update Terraform SQL review rules to use the new typed payload fields after the generic payload and comment fields are removed.
    hcl copy

    resource "bytebase_sql_review" "prod_policy" {
      name        = "projects/my-project/sqlReviews/prod"
      environment = "environments/prod"
    
      rule {
        type  = "column.max-columns"
        level = "SQLReviewRule_WARNING"
        number_payload {
          value = 20
        }
      }
    
      rule {
        type  = "naming.table"
        level = "SQLReviewRule_ERROR"
        naming_payload {
          format          = "^[a-z][a-z0-9_]*$"
          max_length      = 63
        }
      }
    }

    • Adds approval_flow.rules.flow inside bytebase_setting (settings/WORKSPACE_APPROVAL) for Terraform-managed approval flows, replacing risk resources; see approval_flow.tf.
    • SQL review rules in Terraform now use typed payload fields — number_payload, string_payload, string_array_payload, naming_payload — replacing the generic payload and comment fields.
    • Adds risk.level as an optional CELCELCommon Expression Language, an open-source expression language maintained by Google, used to embed lightweight, safe policy evaluation logic into tools without running a full scripting engine. factor for CHANGE_DATABASE approval flows.
    • Renames MaskingException to MaskingExemption in APIs; replaces the member field with a members list; removes the action field; renames Terraform resource masking_exception_policy to masking_exemption_policy.
    • Changes user references from users/{id} to users/{email} across APIs and storage; audit logs now store user emails directly.

    +15 more show less

    • Adds MCP integration support.
    • Adds Workload Identity as a dedicated account type for OIDC-based authentication, with GitHub Actions support.
    • Supports direct messages for Microsoft Teams.
    • Moves rollout policy checkers (Require issue approval and Plan check enforcement) from environment level to project level.
    • Removes the reason field from BatchRunTasks and BatchCancelTaskRuns batch task APIs (reason is now supported only for skip operations).
    • Applies Disallow Copy Policy to Admin and DBA roles, which were previously exempted.
    • Consolidates DDL and DML changes so users no longer need to select them explicitly when initiating a New Plan or configuring an approval flow.
    • Approval flows are now defined directly using CEL expressions, without intermediate risk definitions.
    • Refines database group permissions: roles with bb.projects.get gain bb.databaseGroups.list/get; roles with bb.projects.update gain bb.databaseGroups.create/update/delete.
    • Adds event trigger sync and SDL support for PostgreSQL.
    • Supports TLS/SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. for Trino.
    • Supports passphrase-protected private keys for Snowflake.
    • Adds timeline view, auto-expanded task details, and collapsible task run logs with auto-refresh on the rollout page.
    • Allows filtering in SQL Editor results to quickly locate rows.
    • Allows selecting a database group to query from in the SQL Editor.

    20 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !User references change from users/{id} to users/{email} in all APIs and storage; any integration or script using users/{id} format will break.
    • !The action field is removed from MaskingExemption (formerly MaskingException) in APIs.
    • !MaskingException is renamed to MaskingExemption in APIs; the Terraform resource masking_exception_policy is renamed to masking_exemption_policy.
    • !The member field in masking exemption APIs is replaced with a members list.
    • !The reason field is removed from BatchRunTasks and BatchCancelTaskRuns; reason is now only supported for skip operations.
    • !SQL review rule level enums change from SQLReviewRuleLevel_WARNING/ERROR to SQLReviewRule_WARNING/ERROR in Terraform.
    • !Generic payload and comment fields are removed from SQL review rules in Terraform; typed fields (number_payload, string_payload, string_array_payload, naming_payload) must be used instead.
    • !For Terraform approval flows, risk resources are removed; approval flows must be defined via bytebase_setting (settings/WORKSPACE_APPROVAL) using approval_flow.rules.flow.
    • !Database group permissions are now tied to bb.projects.get and bb.projects.update; custom roles in Terraform must be updated accordingly.
    • !Disallow Copy Policy now applies to Admin and DBA roles, which were previously exempted.
    • !Rollout policy checkers (Require issue approval, Plan check enforcement) have moved from environment to project level; existing configurations are migrated automatically.
    • !Schema Template functionality is removed.
26. 3.12.2 Dec 4, 2025 · release notes

    Bytebase 3.12.2 adds visualized EXPLAIN support for SQL Server and improves Doris syntax compatibility.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.12.2 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.12.2

    └──▷ HOW TO FIND IT
    Visualize query execution plans for SQL Server databases directly within the Bytebase SQL Editor.
    📍In the Bytebase UI, open the SQL Editor for a SQL Server database, write your query, and select the Explain option to view the visualized plan.
    • SQL Server - Add visualized EXPLAIN support in SQL Editor
    • Doris - Improve syntax compatibility

    2 details in Everything

27. 3.12.1 Nov 20, 2025 · release notes

    Bytebase 3.12.1 adds stdout audit logging, AWS cross-account IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. auth, GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. Service Agent role, and BigQueryBigQueryA serverless, cloud-hosted analytical database from Google that runs SQL queries across massive datasets without managing infrastructure, giving cyber tools scalable storage and fast querying over large volumes of log or event data. dry-run SQL validation.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.12.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.12.1

    └──▷ HOW TO FIND IT
    Use the dry-run feature in the Bytebase SQL Editor UI for BigQuery to check syntax without executing changes.
    📍In the Bytebase console, open the SQL Editor for a BigQuery database, paste your query, and click Dry Run.
    • Worksheets gain folder-based organization with nested folders, drag-and-drop reordering, and inline actions (rename, star/unstar, sharing)
    • Project-level data query policies are now available (previously restricted to workspace level only)
    • Cross-account AWS IAMAWS IAMAWS Identity and Access Management is Amazon's service for controlling who and what can call AWS APIs, by attaching policies that allow or deny actions on resources. Cyber tools use it to scope credentials to least privilege. authentication is supported for database connections
    • GitOps Service Agent role added to Bytebase RBACRBACRole-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists. for automated CI/CD workflows
    • BigQuery SQL Editor now supports dry-run execution to validate queries before running them

    5 details in Everything

28. 3.12.0 Nov 6, 2025 · release notes

    Bytebase 3.12.0 adds PostgreSQL State-based GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. workflow, IdP-initiated SSOIdP-initiated SSOA single sign-on flow where the identity provider redirects an already-authenticated user directly to a service provider without the service provider first requesting authentication, removing the need for a separate login prompt., and direct SQL Editor export.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.12.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.12.0

    • Add support for IdP-initiatedIdP-initiatedA SAML or OIDC login flow where the identity provider starts the session and pushes an assertion to the service provider without the user first requesting access, removing the SP-side redirect step. SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. flow.
    • Allow direct data export in SQL Editor for users who can run the query — no approval issue is created. The approval flow still applies to export requests submitted through Data Export Center. You can also disable data export at the workspace level, so that SQL Editor queries cannot be exported directly by default.
    • Support data export for multi-statement queries in SQL Editor.
    • Update APP_IM configuration format in API and UI.

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Remove identity provideridentity providerA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. permissions from the Workspace DBA role.
    • !Remove support for URL-based secret retrieval via URL template format.
    • !Deprecate changelist feature.
    • !Update APP_IM configuration format in API and UI.
29. 3.11.1 Oct 23, 2025 · release notes

    Bytebase 3.11.1 adds Apache Doris system view support, inactive session timeout config, and multi-query result export

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.11.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.11.1

    └──▷ HOW TO FIND IT
    Export results of multiple ad-hoc SQL queries in the Bytebase UI to a CSV/Excel file for analysis.
    📍In the Bytebase console, run multiple queries and use Export › All results.
    • Apache Doris - Add support for system views and functions in SQL Editor.
    • Add support for configuring inactive_session_timeout to limit idle database sessions.
    • Support exporting results from multiple queries into a single output.

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The --check-plan option is removed from the bytebase-action rollout command; scripts using this flag will fail.
30. 3.11.0 Oct 10, 2025 · release notes

    Bytebase 3.11.0 introduces configurable rollout requirements, Terraform enum updates, AWS Elasticsearch cross-account support, and instance labels.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.11.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.11.0

    • Adds Require Issue Approval and Plan Check Enforcement as configurable rollout requirements to control issue deployment behavior
    • Supports key-value instance labels for database instances
    • Adds pre-flight validation and circuit breaker to the gh-ost workflow

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Environment rollout policy now requires bb.taskRuns.create permission for manual rollouts; Issue Creators and Last Issue Approvers can no longer roll out issues automatically
    • !Deprecates bb.sql.export permission and roles/projectExporter role; use appropriate task permissions instead
    • !Replaces request.row_limit in project IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. policy with maximum_result_rows in QueryDataPolicy
    • !Standardizes CELCELCommon Expression Language, an open-source expression language maintained by Google, used to embed lightweight, safe policy evaluation logic into tools without running a full scripting engine. attribute naming to prefixes resource.*, statement.*, request.* (e.g., environment_id becomes resource.environment_id)
    • !Unifies risk levels to single RiskLevel enum strings (LOW, MODERATE, HIGH) instead of integers (100, 200, 300); CEL expressions must change from level == 300 to level == "HIGH"
    • !Simplifies approval template to singleton with flat role array; replaces approval_finding_done/approval_finding_error with approval_status enum
    • !Consolidates task types into DATABASE_MIGRATE (with migrate_type: DDL/DML/GHOST) and DATABASE_SDL; splits changelog Type into Type and MigrationType enums; merges DatabaseSchemaUpdate and DatabaseDataUpdate into DatabaseUpdate
    • !Terraform provider: uses RiskLevel enum instead of numeric values for level in bytebase_risk
    • !Terraform provider: removes disable_copy_data_policy; moved into query_data_policy as the disable_copy_data field
    • !Terraform provider: updates structure of the approval_flow setting
    • !Terraform provider: removes row_limit from bytebase_iam_policy setting
    • !Removes Format on Save feature from SQL Editor
31. 3.10.1 Sep 25, 2025 · release notes

    Bytebase 3.10.1 adds project labels (64 key-value pairs), transaction mode toggle in Plan, and MySQL isolation level selection

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.10.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.10.1

    • Add labels field to projects, supporting up to 64 key–value pairs for metadata tagging
    • Add option to switch transaction mode in Plan UI/CLI
    • Add MySQL isolation level selection when transaction mode is enabled in Plan
    • Add role selection for executing SQL in Plan (Postgres)
    • Support instance_id field in risk condition filters

    +2 more show less

    • New API syntax for database label filter: labels.region == "asia"
    • Display tasks in a flat list on the Data Export issue page instead of grouped by stages

    7 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The standalone API field DisableCopyDataPolicy is removed; use QueryDataPolicy instead.
    • !Database label filter syntax changed from label == "region:asia" to labels.region == "asia"
32. 3.10.0 Sep 11, 2025 · release notes

    Bytebase 3.10 adds Cassandra data masking, a TLS verification toggle for instance setup, and GitHub ActionsGitHub ActionsGitHub's built-in CI/CD system that runs automated workflows triggered by repository events, letting cyber tools automate testing, building, and releasing without managing separate pipeline infrastructure. job summaries

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.10.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.10.0

    • Add support for data masking in Cassandra databases.
    • Add a new option to toggle TLS certificate verification when adding a database instance.
    • Enable the rollout command in the Bytebase GitHub Action (bytebase-action) to output a job summary.

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The SQL_RESULT_SIZE_LIMIT setting and DATA_EXPORT policy are deprecated; use DATA_QUERY policy instead, where sql_query_restriction and data_export settings have been consolidated.
    • !In Terraform, the sql_query_restriction block is deprecated; replace it with a query_data_policy block supporting disable_export, maximum_result_rows, maximum_result_size, and timeout_in_seconds.
33. 3.9.2 Aug 28, 2025 · release notes

    Bytebase 3.9.2 adds hard-delete for projects/instances, draft plan modification, Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. SCIMSCIMA standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. normalization, PostgreSQL CREATE RULE support, and API pagination/filtering.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.9.2 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.9.2

    • Adds the ability to hard-delete projects and instances after they are archived
    • Adds support for adding or removing changes in draft plans
    • Streamlines approval workflows with a new 'one-click ready for review' action
    • Updates UpdateMask values in the UpdatePolicy API to follow AIP conventions (field names only, no oneof type names)
    • Adds normalization of SCIM user emails to lowercase when authenticating via Entra ID

    +6 more show less

    • Adds support for the PostgreSQL CREATE RULE statement in the SQL editor
    • Adds pagination and filtering capabilities to the Group API endpoint
    • Adds support for empty environments in Terraform instance and database resources
    • Adds support for filters in Terraform group list data sources
    • Updates Terraform masking_exception_policy to support the raw_expression field, which overrides other masking fields when provided
    • Deprecates column, member, and action fields in the Terraform masking_exception_policy in favor of their pluralized counterparts

    11 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The UpdateMask values in the UpdatePolicy API now omit oneof type names, using field names only (see PR #17240)
34. 3.9.1 Aug 14, 2025 · release notes

    Bytebase 3.9.1 adds file-backed PG_URL hot-reload, AWS OpenSearchOpenSearchAn open-source search and analytics engine, forked from Elasticsearch by AWS in 2021, that lets cyber tools store, query, and visualize large volumes of log or event data without licensing restrictions. IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. auth, and Terraform sync_databases/masking exceptions

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.9.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.9.1

    • Adds PG_URL file reading with hot-reload support
    • Adds AWS OpenSearch IAM authentication support
    • Adds sync_databases attribute to Terraform instance resource
    • Adds masking exception configuration in Terraform to skip specific databases, tables, or columns across a project

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The deprecated --pg command-line flag is removed; use the PG_URL environment variable for external PostgreSQL connections instead.
    • !The --disable-metric flag is replaced by a Workspace setting (the CLI flag no longer exists).
    • !The --disable-sample flag is removed.
35. 3.9.0 Jul 31, 2025 · release notes

    Bytebase 3.9.0 introduces a new database CI/CD experience with multi-task rollback and plan draft staging.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.9.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.9.0

    • Enables a new database CI/CD workflow by default, splitting the interface into Overview, Changes, and Rollout tabs for batch change management
    • Adds Multi-task rollback to the Rollout tab, allowing multiple tasks to be rolled back simultaneously
    • Adds Plan draft capability to stage database changes before deployment

    3 details in Everything

36. 3.8.1 Jul 17, 2025 · release notes

    Bytebase 3.8.1 adds preview database CI/CD workflow, SQL Server spatial index support, and Redshift txn-mode directive.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.8.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.8.1

    • -- txn-mode=off directive supports turning off transaction wrapping in Redshift
    • Terraform rollout policy supports environments
    • Terraform copy data policy supports environments and projects
    • Terraform data source query policy supports environments and projects
    • Data export files are available for 24 hours with unlimited downloads during that period

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !default_expression, default_string, and default_null fields in ColumnMetadata are removed from the API; use the unified default field instead.
37. 3.8.0 Jul 3, 2025 · release notes

    Bytebase 3.8.0 adds query result row limits and multi-domain configuration support

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.8.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.8.0

    • Adds query result row limit support to control the number of rows returned by queries
    • Add multi-domain configuration support for environments with multiple domains

    2 details in Everything

38. 3.7.1 Jun 19, 2025 · release notes

    Bytebase 3.7.1 adds use_ssl field for Terraform database connection SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. certificates and moves Review Center to /plans.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.7.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.7.1

    └──▷ USE IT
    Configure a database resource in Terraform to enforce SSL connections.
    hcl copy

    resource "bytebase_database" "example" {
      # ...
      use_ssl = true
    }

    Update any bookmarks or scripts referencing the old Review Center URL path.
    📍https://<your-bytebase-instance>/plans
    • Adds use_ssl field in Terraform provider to control SSL certificate application for database connections
    • Moves Review Center routes from /review-center to /plans

    2 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Review Center routes have changed from /review-center to /plans, breaking any direct links or bookmarks to the old paths.
39. 3.7.0 Jun 5, 2025 · release notes

    Bytebase 3.7 adds batch data export via issues, Trino data masking, and SQL Editor enhancements.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.7.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.7.0

    └──▷ TRY IT
    Schedule batch tasks using the new API field after migration from the deprecated Plan structure.
    copy

    $ POST /api/v1/space/{spaceKey}/plan
    {
      "projectName": "my_project",
      "title": "batch_export",
      "specs": [ ... ],
      "targets": [ ... ]
    }

    Create a plan with the new release parameter for database configuration changes.
    copy

    $ PATCH /api/v1/database/{name}
    {
      "config": {
        "type": "MYSQL",
        "release": "v3.7"
      }
    }

    • Plan.spec field earliest_allowed_time removed; use run_at in BatchRunTasksRequest for scheduling
    • Plan fields steps and target renamed to specs and targets respectively
    • PlanService.PreviewPlan RPCRPCRemote Procedure Call, a protocol that lets a program execute a function on another machine as if it were local, giving cyber tools a structured way to communicate across processes or hosts without managing raw sockets. removed from the API
    • ChangeDatabaseConfig now uses release field and has dropped BASELINE from Type and schema_version
    • Support batch data export from multiple databases or a database group via issue

    +5 more show less

    • Support batch data export from limited databases in the SQL Editor
    • Trino supports data masking
    • MariaDB supports sql_type in risk condition
    • SQL Server supports columnstore index
    • EARLIEST_ALLOWED_TIME setting removed; use SCHEDULED_TIME during rollout

    10 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The earliest_allowed_time field is removed from Plan.spec; migrate to using run_at in BatchRunTasksRequest
    • !The steps and target fields are removed from Plan; use specs and targets respectively
    • !The PreviewPlan RPC is removed from PlanService
    • !For ChangeDatabaseConfig, the BASELINE value is removed from Type, the schema_version field is removed, and a new release field is added
    • !Setting names are updated to match SettingName proto definitions; existing configurations may need mapping updates
40. 3.6.2 May 23, 2025 · release notes

    Bytebase 3.6.2 adds database group queries, local query history, lazy execution to SQL Editor

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.6.2 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.6.2

    • Adds support for database groups in the batch query interface of the SQL Editor.
    • Stores SQL query result history locally in the browser within the SQL Editor.
    • Implements lazy query execution in the SQL Editor, running requests only when a tab is clicked.
    • Enables display of SQL Server trigger bodies in the SQL Editor.

    4 details in Everything

41. 3.6.1 May 8, 2025 · release notes

    Bytebase 3.6.1 adds DML rollback for unique indexes and parallel rollout tasks

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.6.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.6.1

    • DML rollback now supports unique indexes for MySQL, PostgreSQL, Oracle and MSSQL

    1 detail in Everything

42. 3.6.0 Apr 24, 2025 · release notes

    Bytebase 3.6.0 adds Trino/Cassandra support, OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. group sync, PostgreSQL lock retry, and EXPLAIN for MSSQL/Redis read-only commands

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.6.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.6.0

    • Adds basic support for the Trino database engine as a new datasource type
    • Supports syncing OIDC IdPIdPA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems. groups to Bytebase groups via the groups claim
    • Adds execution support for Cassandra statements in SQL editor and issue resolution
    • Automatically retries PostgreSQL lock timeouts during statement execution
    • Adds EXPLAIN query support for MSSQL in the SQL editor

    +3 more show less

    • Supports more read-only commands for Redis in the SQL Editor
    • Improves columns auto-completion in FROM clause for MSSQL
    • Allows filtering tasks by status in UI when an issue involves more than 10 databases

    8 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Remove EnvironmentService API and permissions; grant bb.settings.update to roles instead of bb.environments.*
    • !Remove predefined groupValue enum from ApprovalNode, restricting assignments to role only
    • !Deprecate Anomaly Center; schema drift must now be viewed in the database list or database page
43. 3.5.2 Apr 10, 2025 · release notes

    Bytebase 3.5.2 adds Cassandra SQL Editor support and pagination for list instances API

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.5.2 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.5.2

    • Support Cassandra in SQL Editor enables querying and managing Cassandra databases directly within the Bytebase SQL Editor interface.

    1 detail in Everything

    └──▷ BREAKING ON UPGRADE

    • !The list instance API now returns at most 10 instances by default instead of all; you must use the pagination parameter to fetch more.
    • !The statement field in the Release API is now returned as a base64-encoded string.
44. 3.5.1 Mar 28, 2025 · release notes

    Bytebase v3.5.1 adds Cosmos DB SQL syntax support and OpenSearchOpenSearchAn open-source search and analytics engine, forked from Elasticsearch by AWS in 2021, that lets cyber tools store, query, and visualize large volumes of log or event data without licensing restrictions. connectivity via Elasticsearch client.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.5.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.5.1

    • SQL Editor now supports WHERE clauses and SELECT projections for the Cosmos DB SQL syntax.

    1 detail in Everything

45. 3.5.0 Mar 13, 2025 · release notes

    Bytebase 3.5.0 adds Azure IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. Auth for Cosmos DB & SQL, paginated APIs, and DingTalk direct message webhooks

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.5.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.5.0

    • Adds page_size and page_token query parameters to GET /v1/projects for paginated project listing
    • Adds name and resource_id filter parameters to POST /v1/projects:search endpoint
    • Adds filter parameters (environment, project, instance, name, engine, label, exclude_unassigned) to GET /v1/instances/{instance}/databases for database listing
    • Adds filter parameters (name, email, user_type, state) to GET /v1/users for user listing
    • Supports Azure IAM authentication for Cosmos DB and Azure SQL connections

    +3 more show less

    • Adds webhook direct message support for DingTalk integration
    • Allows updating the plan for database group deployment via the extended API
    • Configures custom maximum query time in SQL Editor via Workspace Settings -> General -> Security -> Maximum query time

    8 details in Everything

46. 3.4.1 Feb 27, 2025 · release notes

    Bytebase 3.4.1 adds Terraform provider support for custom roles, instance licenses, and external secrets; enables new migration flags.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.4.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.4.1

    • Adds custom_roles, semantic_types, and database resources to the Bytebase Terraform provider
    • Adds ability to assign instance licenses via the Terraform provider
    • Enables the throttle-control-replicas flag for online migration
    • Enables the attempt-instant-ddl flag for online migration

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !External Approval is deprecated; users must use the Bytebase API for managing approvals and rollouts.
    • !MySQL online migration sync and cutover tasks are consolidated into a single task, requiring a bbdataarchive database to be created first.
47. v3.4.0 Feb 13, 2025 · release notes

    Index Advisor and SQL Sharing move to the free Community Plan; task check summary report gains Redshift support.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch v3.4.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout v3.4.0

    └──▷ HOW TO FIND IT
    Get index suggestions for slow queries via the Index Advisor.
    📍Set up OpenAI integration in Bytebase settings to enable the free Community Plan Index Advisor feature.
    Star and share worksheets with your team using the new SQL Sharing feature on the Community Plan.
    📍Use the star/share options in the SQL Editor to collaborate.
    View Redshift-specific summary reports for task checks.
    📍Check task check results for Redshift databases to see affected rows and statement reports.
    • Index Advisor feature is available in the Community Plan (free), enabling the suggestion of indexes for slow queries once OpenAI integration is set up
    • SQL Sharing feature is available in the Community Plan (free), allowing users to star and share worksheets with their team in the SQL Editor
    • The summary report of task check supports Redshift, including affected rows and statement reports

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The redundant key attribute of project has been removed.
48. 3.3.1 Jan 30, 2025 · release notes

    Bytebase 3.3.1 adds 1-click DML rollback for Oracle, Vault AppRole auth, and partial-line execution in SQL Editor.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.3.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.3.1

    └──▷ HOW TO FIND IT
    Rollback a DML change in Oracle using the new one-click feature.
    📍In the UI, navigate to the change history for an Oracle instance and select 1-click DML rollback.
    Connect Bytebase to Vault using AppRole authentication.
    📍When configuring a new connection, select AppRole as the method under the Vault provider settings.
    Execute only the current line's query instead of the whole block using the keyboard shortcut.
    📍Position cursor in SQL Editor and press Cmd+Enter.
    • Adds 1-click DML rollback support for Oracle database instances
    • Adds AppRole method option for connecting to Vault as an authentication mechanism
    • Enables pressing Cmd+Enter in SQL Editor to execute the query on the current line where the cursor is located
    • Adds compatibility with PostgreSQL extension CITUS

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The concise parameter has been removed from GetChangelog and GetDatabaseSchema APIs, so calls relying on this parameter will fail.
49. 3.3.0 Jan 16, 2025 · release notes

    Bytebase 3.3.0 adds Release workflow, CosmosDB support, self-approval settings, and PostgreSQL 17/materialized view coverage.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.3.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.3.0

    • Introduces Release, a new versioned database schema migration workflow for bundling and deploying scripts.
    • Adds support for CosmosDB as a target database system.
    • Adds project setting to allow users to self-approve their own issues.
    • Extends Schema Synchronization to support PostgreSQL materialized views.
    • Adds preliminary support for PostgreSQL 17.

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Global masking takes precedence over column masking (previously, column masking took precedence).
    • !Masking levels are eliminated; semantic types map directly to masking algorithms.
50. 3.2.0 Jan 2, 2025 · release notes

    Bytebase 3.2.0 adds selective DB sync, Redshift/ClickHouse definition views, and a new Changelog API.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.2.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.2.0

    • Add selective database syncing to pull specific databases from an instance instead of syncing the entire environment
    • Expose TABLE and VIEW DDL definitions in the UI for Amazon Redshift and ClickHouse engines
    • Introduce the new Changelog API to replace the deprecated ChangeHistory API endpoint
    • Enable SQL Editor evaluation of special date/time values such as infinity in PostgreSQL

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The ChangeHistory API endpoint has been removed; calls must now target the Changelog API instead.
    • !UI-initiated changes no longer include a version number in their payload, breaking workflows relying on that field.
51. 3.1.2 Dec 19, 2024 · release notes

    Adds Lark IM/webhook integration, Redshift view definitions, and UI improvements

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.1.2 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.1.2

    • Supports IM and webhook integration for Lark
    • Display table and view definition for Redshift in SQL Editor

    2 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The masking policy API v1/{instance}/{database}/policies/masking is removed; use v1/{instance}/{database}/metadata with the columnConfigs parameter instead.
52. 3.1.1 Dec 5, 2024 · release notes

    Bytebase 3.1.1 adds customizable homepage, Redis ClusterRedis ClusterA distributed mode of Redis, the open-source in-memory data store, that automatically shards data across multiple nodes and keeps it available if some nodes fail, giving cyber tools low-latency shared state at scale. node queries, and improved SQL Editor capabilities.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.1.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.1.1

    • Customizable homepage with a user-defined shortcut list

    1 detail in Everything

    └──▷ BREAKING ON UPGRADE

    • !Instance roles are removed from Database messages; use GetInstance or ListInstanceRoles to get instance role information.
53. 3.1.0 Nov 21, 2024 · release notes

    Bytebase 3.1.0 adds PostgreSQL role selection, SQL Review Rules, SQL permission refactoring, and environment color customization.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.1.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.1.0

    • bb.sql.select, bb.sql.dml, bb.sql.ddl, bb.sql.explain, bb.sql.info, bb.sql.export, and bb.sql.admin permissions replace the old bb.databases.* permission keys for SQL Editor access control.
    • roles/projectQuerier role renamed to roles/sqlEditorUser
    • Support PostgreSQL role selection in DDL/DML issues, defaulting to instance connection user unless database tenant mode is on.
    • PostgreSQL database tenant mode option added to project settings to manage multitenancy for PostgreSQL databases.
    • New SQL Review Rules available for MySQL: Prohibit DDL on specific tables and Prohibit DML on specific tables.

    +1 more show less

    • Ability to set custom colors for environments to improve visual distinction in the UI.

    6 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Permission key bb.databases.query is renamed to bb.sql.select
    • !Permission key bb.databases.queryDML is renamed to bb.sql.dml
    • !Permission key bb.databases.queryDDL is renamed to bb.sql.ddl
    • !Permission key bb.databases.queryExplain is renamed to bb.sql.explain
    • !Permission key bb.databases.queryInfo is renamed to bb.sql.info
    • !Permission key bb.databases.export is renamed to bb.sql.export
    • !Permission key bb.instances.adminExecute is renamed to bb.sql.admin
    • !Role roles/projectQuerier is renamed to roles/sqlEditorUser
    • !The database field of sheet in SheetService API is removed
54. 3.0.1 Nov 7, 2024 · release notes

    Bytebase 3.0.1 adds environment policies for DDL/DML execution, BigQueryBigQueryA serverless, cloud-hosted analytical database from Google that runs SQL queries across massive datasets without managing infrastructure, giving cyber tools scalable storage and fast querying over large volumes of log or event data. data masking, and SQL review upsert API

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.0.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.0.1

    └──▷ TRY IT
    Upsert a SQL review configuration using the new PATCH endpoint.
    copy

    $ curl -X PATCH "https://<bytebase-host>/api/v1/reviewConfigs/<project-key>?allow_missing=true" -H 'Content-Type: application/json' -d '{"config": {}}'

    Enable data access control and masking for a project via the UI.
    📍In the console, go to a Project › Access Control page and configure the masking rules.
    • Add an environment policy to allow executing DDL/DML statements directly in SQL Editor.
    • Support data masking for BigQuery.
    • Add data access control and masking page under each project.
    • SQL review configuration API supports upsert via PATCH.

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Issue creators are no longer allowed to approve their own issues.
    • !The SQL review configuration API now uses PATCH for upserts (e.g., PATCH /v1/reviewConfigs/{not exist}?allow_missing=true).
55. 3.0.0 Oct 24, 2024 · release notes

    Bytebase 3.0 adds AI SQL generation, gh-ost support for MariaDB, and 1-click rollback for SQL Server DML.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 3.0.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 3.0.0

    └──▷ USE IT
    Use the new allow_missing parameter to create a group if it does not already exist.
    shell copy

    curl -X PATCH 'https://<bytebase-host>/api/v1/groups/not_exist_group?allow_missing=true'

    • Adds an AI Assistant to the SQL Editor that can generate SQL from natural language prompts, explain queries, and identify potential issues
    • Supports 1-click rollback for SQL Server DML change tasks
    • Enables gh-ost online schema changes for MariaDB databases
    • Introduces new SQL review rules requiring MAX_EXECUTION_TIME for MySQL, MAX_STATEMENT_TIME for MariaDB, and specific ALGORITHM and LOCK options for online DDL in MySQL/MariaDB, plus table/column comment checks for PostgreSQL/Oracle
    • Adds a rule to disallow mixing statements within the same DDL or DML task during SQL review

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !CELCELCommon Expression Language, an open-source expression language maintained by Google, used to embed lightweight, safe policy evaluation logic into tools without running a full scripting engine. parsed expressions no longer include unused sourceInfo, which impacts the structure of responses from /v1/cel/batchDeparse, /v1/cel/batchParse, and all IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. policy endpoints (/v1/workspaces/*:getIamPolicy, /v1/workspaces/*:setIamPolicy, /v1/projects/{project}:getIamPolicy, /v1/projects/{project}:setIamPolicy).
    • !The group_email parameter is now mandatory when calling POST /v1/groups to create a new group.
56. 2.23.1 Oct 10, 2024 · release notes

    Bytebase 2.23.1 adds database group changelist application and MySQL classification comment rule

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.23.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.23.1

    • Support applying changelists to database groups.
    • Add a SQL Review rule for MySQL: Enforce classification in table/column comment.

    2 details in Everything

57. 2.23.0 Sep 19, 2024 · release notes

    Bytebase 2.23 adds Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. SCIMSCIMA standard for creating, updating and removing user accounts and groups across applications. It helps an identity provider keep access in sync when people join, change roles or leave. sync, CockroachDB support, and project-level backup settings

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.23.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.23.0

    • Adds Entra ID (Azure AD) user and group synchronization via SCIM.
    • Adds native support for the CockroachDB database engine.
    • Adds project-level backup settings with auto-enable and skip error options.
    • Adds real-time syntax checking in the SQL Editor.
    • Adds ability to configure password restriction policies.

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The Data Classification upload data format has changed from a list to a key-value map.
58. 2.22.3 Sep 5, 2024 · release notes

    Bytebase 2.22.3 adds one-click rollback for PostgreSQL DML changes and allows enabling backups after issue creation.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.22.3 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.22.3

    └──▷ HOW TO FIND IT
    Revert a deployed PostgreSQL DML change by triggering the rollback action in the UI
    📍In the Bytebase UI, open the PostgreSQL DML issue and click One-click rollback to reverse the data changes.
    Enable DML backup for an existing issue that was created without it
    📍Open the existing change issue in Bytebase, locate the backup settings section, and toggle the Enable Backup option.
    • Adds one-click rollback capability for PostgreSQL DML changes, allowing users to reverse data modifications directly from the change record.
    • Adds the ability to enable or disable the backup option for an issue even after it has been created, previously requiring this to be set before creation.

    2 details in Everything

59. 2.22.2 Aug 22, 2024 · release notes

    Bytebase 2.22.2 adds workspace-level group roles, SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management.-only enforcement, and a new PostgreSQL review rule.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.22.2 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.22.2

    • Allow assigning roles to groups at the workspace level
    • Support disallowing sign-in with email and password, allowing only SSO
    • Add a PostgreSQL SQL review rule: Disallow setting volatile default values on columns

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The change histories page in the project has been removed; history is now located on the database page.
    • !BranchService.DiffDatabase API is no longer available.
    • !SQLService.DifferPreview API is no longer available.
60. 2.22.1 Aug 8, 2024 · release notes

    Bytebase 2.22.1 adds SQL Editor schema details, GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. PR review support, Microsoft Entra SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management., and Open NL2SQL to Community plan.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.22.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.22.1

    • Add Microsoft Entra as a built-in OAuth2OAuth2An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs. SSO provider for authentication
    • Enable natural language to SQL (NL2SQL) in the SQL Editor via the OpenAI feature on the Community Plan by configuring your own OpenAI key
    • Support SQL reviews via PR comments for GitOps workflows
    • Add support for selecting data sources between Admin and Readonly modes in the SQL Editor, configurable at the environment or project level
    • Support using database labels as filters for database group conditions in raw expression format

    5 details in Everything

61. 2.22.0 Jul 25, 2024 · release notes

    Bytebase 2.22.0 adds PostgreSQL blocking session monitoring, Oracle auto-completion, Hive KerberosKerberosA network authentication protocol that uses tickets issued by a trusted service. Users and services can prove their identities without sending a password to each application. auth, and SQL Server MS_Description sync

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.22.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.22.0

    • Support monitoring blocking sessions during PostgreSQL task execution.
    • Support auto-completion for Oracle.
    • Support Kerberos authentication for Hive.
    • Sync extended property MS_Description on Table/Column as comment for SQL Server.

    4 details in Everything

62. 2.21.0 Jul 11, 2024 · release notes

    Bytebase 2.21.0 adds Redis Sentinel/Cluster support, per-engine SQL review rules, and WeCom DMs.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.21.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.21.0

    • redis.sentinel and cluster connection modes supported for instance configuration.
    • SQL review rules can be configured per database engine.
    • New auto_close_issue_after_rollout setting in project settings to automatically close issues after rollout completion.
    • WeCom direct messages enabled for issue activity notifications.
    • Project settings now include an option to allow SQL editing after issue creation.

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Multi-tenancy configuration has been moved from project to database group.
63. 2.20.0 Jun 27, 2024 · release notes

    Bytebase 2.20 adds Databricks support, SQL Server TLS/SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination., Lark notifications, and email domain restrictions.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.20.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.20.0

    • Adds Databricks database engine support
    • Adds TLS/SSL connection option for SQL Server databases
    • Adds Lark direct notifications for issue activities via webhook events
    • Adds email domain restriction configuration for user sign-up
    • Adds ability to configure different SQL review policies for different projects

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The classification sync config has been moved from the database setting to the workspace setting
    • !SQL Editor read-only mode now allows only Redis read-only commands
64. 2.19.0 Jun 13, 2024 · release notes

    Bytebase 2.19 adds DynamoDB support, standalone SQL review issues, and prioritization flags for querier/exporter.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.19.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.19.0

    • Adds DynamoDB as a supported database type
    • Enables creating standalone SQL review issues not tied to deployments
    • Supports receiving issue activity notifications via Slack direct messages
    • Adds prior backup support for PostgreSQL migrations
    • Adds Disallow redundant indexes SQL Review Rule for SQL Server

    +1 more show less

    • Adds maximum role expiration time configuration for querier and exporter

    6 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Creating multiple-database issues now shares SQL statements among databases instead of keeping them separate.
65. 2.18.0 May 30, 2024 · release notes

    Adds BigQueryBigQueryA serverless, cloud-hosted analytical database from Google that runs SQL queries across massive datasets without managing infrastructure, giving cyber tools scalable storage and fast querying over large volumes of log or event data. support, user groups, SQL Server sync schema, and new SQL review rules for SQL Server.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.18.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.18.0

    • Adds BigQuery as a supported database platform for instance connection.
    • Supports user groups to manage permissions and access control.
    • Enables Sync Schema for SQL Server to keep local schema definitions in sync with the remote database.
    • Supports MongoDB cluster topology and direct node connections within a cluster.
    • Adds detailed issue task execution logs display for SQL Server and Oracle databases.

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The issue assignee feature is removed, so issues can no longer be assigned to specific users.
    • !Table groups are removed, meaning previous table grouping configurations will be lost or ignored.
    • !Plan-related gRPCgRPCAn open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. endpoints have been migrated from RolloutService to PlanService, requiring client updates to point to the correct service.
66. 2.17.0 May 16, 2024 · release notes

    Bytebase 2.17.0 adds issue label configuration, granular SQL review rules for PostgreSQL/MySQL, and audit log filtering by method.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.17.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.17.0

    • labels configuration added to issues to tag and organize them within the system.
    • New schema_snapshots support for displaying database snapshots in SQL Server environments.
    • Import functionality extended to accept changelists from zip or SQL file formats.
    • Audit logs can now be filtered by specific method and project identifiers.

    4 details in Everything

67. 2.16.0 May 2, 2024 · release notes

    Bytebase 2.16.0 adds AWS Secrets Manager storage for DB passwords and IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access.-based connections to Google Cloud SQL.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.16.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.16.0

    • Support storing database passwords in AWS Secrets Manager
    • Support IAM-based connections to Google Cloud SQL for MySQL and PostgreSQL

    2 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Manage on Database Mode is deprecated for Oracle; only Schema Mode is supported
68. 2.15.0 Apr 11, 2024 · release notes

    Bytebase 2.15 introduces GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. workflow, HashiCorp Vault secret integration, and Apache Hive support

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.15.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.15.0

    • Adds new GitOps workflow with support for multiple VCSVCSVersion control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. connectors per project and database group targeting in VCS connector configuration
    • Enables HashiCorp Vault as an external data source for database secrets via the instance settings
    • Adds Apache Hive database platform support for connection and management
    • Introduces one-time data export issue type for ad-hoc data retrieval tasks
    • Adds SQL review rules for PostgreSQL: detecting non-transactional statements and enforcing NOT VALID for foreign key creation

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Database name templates and latest schema write-back features are deprecated in favor of the new GitOps configuration.
69. 2.14.1 Mar 21, 2024 · release notes

    Bytebase 2.14.1 adds Oracle branching, project-level SQL review rules, and restructured access controls.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.14.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.14.1

    • allUsers is now accepted as a project member with the Querier role for workspace-level query/export functionality previously available in Workspace Settings
    • SQL Review rules added to disallow mixing DDL and DML statements and mixing UPDATE, INSERT, DELETE on the same table
    • SQL Editor Worksheets visibility options updated to Private, Project Read, and Project Write
    • Support for Branching added for Oracle databases

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The option to query and export at the workspace level is no longer available; use allUsers as a project member with the Querier role instead
    • !The feature to prevent copying data from the SQL Editor has been moved to the environment page
70. 2.14.0 Mar 7, 2024 · release notes

    Bytebase 2.14 adds custom roles, BitBucket SQL Review CI, cross-database data masking, and shareable table links

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.14.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.14.0

    • custom roles with specific permissions allow fine-grained access control for teams
    • new SQL Review CI for BitBucket integration enables automated review workflows in BitBucket Pipelines
    • cross-database queries can now be used within data masking operations to reference tables in other databases

    3 details in Everything

71. 2.13.2 Feb 4, 2024 · release notes

    Bytebase 2.13.2 adds new language support and configurable data masking algorithms.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.13.2 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.13.2

    └──▷ HOW TO FIND IT
    View large query results more readably by switching the result grid to vertical orientation.
    📍In the Query Editor, toggle Vertical View in the view options menu.
    • Adds masking_algorithms configuration for defining how sensitive data columns are masked.
    • Supports displaying query results in a vertical format view.

    2 details in Everything

72. 2.13.1 Jan 11, 2024 · release notes

    Bytebase 2.13.1 adds DML pre-backup for MySQL, instance connection limits, data compression/encryption, and renamed API roles.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.13.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.13.1

    • Enables compression and encryption for exported data via API settings
    • Allows editing database indexes directly in the Schema Editor UI

    2 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Bytebase API predefined roles have been renamed: Workspace level OWNER->workspaceAdmin, DBA->workspaceDBA, DEVELOPER->workspaceMember; Project level OWNER->projectOwner, DEVELOPER->projectDeveloper, QUERIER->projectQuerier, EXPORTER->projectExporter, VIEWER->projectViewer, RELEASER->projectReleaser
73. 2.13.0 Dec 28, 2023 · release notes

    Bytebase v2.13 adds support for StarRocks and advanced SQL auto-completion for PostgreSQL, Redshift, and RisingWave.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.13.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.13.0

    • Adds StarRocks database platform support
    • Enables displaying index DDL in the SQL Editor

    2 details in Everything

74. 2.12.0 Dec 14, 2023 · release notes

    Bytebase 2.12.0 adds advanced SQL auto-completion for MySQL, PostgreSQL partition support, TiDB 7.5 compatibility, and UI-based classification JSON import.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.12.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.12.0

    └──▷ HOW TO FIND IT
    Import your organization's data classification schema directly into the application without using the API.
    📍Open Bytebase UI › Settings › Data Management › Import Classification JSON Data
    • Adds advanced SQL auto-completion capability for MySQL databases within the SQL Editor
    • Enables importing classification JSON data directly through the user interface
    • Adds support for displaying and querying partition tables in the SQL Editor for PostgreSQL

    3 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !The existing Enterprise trial license is sunset; users must request a new trial license to continue using that tier.
75. 2.11.1 Nov 23, 2023 · release notes

    Bytebase 2.11.1 adds customizable data masking and issue state webhooks

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.11.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.11.1

    • Adds customizable Masking Algorithms and Semantic Types for Data Masking to control how sensitive data is redacted in queries.
    • Adds webhook notifications when an issue reaches the Waiting for Rollout or Approved states.

    2 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Workspace Owners are now referred to as Workspace Admins in UI and documentation.
    • !Workspace Developers are now referred to as Members in UI and documentation.
    • !User page URL path changed from /u/{uid} to /users/{email}.
76. 2.11.0 Nov 9, 2023 · release notes

    Bytebase 2.11.0 adds MySQL online schema change parameters, a database viewer role, and OceanBase Oracle Mode support

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.11.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.11.0

77. 2.10.0 Oct 26, 2023 · release notes

    Bytebase 2.10.0 adds branch protection rules, database/column labels, table classification, releaser role sets, and query abort.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.10.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.10.0

    • Adds branch protection rules for projects to control merge paths and required approvals
    • Adds the ability to set labels on databases via UI or API
    • Adds the ability to set labels on columns via UI or API
    • Adds table classification configuration per table
    • Adds flexible releaser options: appoint by dedicated role set or last approver of a custom approval process

    +2 more show less

    • Enables aborting long-running queries in the SQL Editor
    • Supports PostgreSQL 16 as a database engine

    7 details in Everything

78. 2.9.1 Oct 12, 2023 · release notes

    Bytebase 2.9.1 adds changelists, multi-db batch queries, external secret manager integration, and PostgreSQL/TiDB branching

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.9.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.9.1

    • Group changes into a changelist and apply them in one issue or export
    • Batch query on multiple databases with selected labels in SQL Editor
    • Integrate an external secret manager to store database credentials
    • Enable branching for PostgreSQL and TiDB

    4 details in Everything

79. 2.9.0 Sep 28, 2023 · release notes

    Bytebase 2.9 introduces SQL Review checks prior to issue creation and predefined table templates for schema design.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.9.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.9.0

    • Run SQL Review checks before the issue is created enables pre-commit style validation by running SQL review rules prior to creating a new issue.

    1 detail in Everything

80. 2.8.0 Sep 14, 2023 · release notes

    Bytebase 2.8.0 adds MySQL parser-based data masking, Oracle schema sync, and a new Affected Rows risk factor.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.8.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.8.0

    • Adds MySQL parser-based data masking for granular access control configuration
    • Adds support for syncing schema to Oracle databases

    2 details in Everything

81. 2.7.0 Aug 31, 2023 · release notes

    Bytebase 2.7.0 adds Git-like branching for schema migration, Issue history search, and Audit Log export

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.7.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.7.0

    • Supports Git-like branching workflow for database schema migration changes, enabling parallel development tracks within the same project
    • Enables searching across all historical data within Issues to locate past comments, status changes, or approval records
    • Adds capability to export Audit Logs for compliance and external SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. integration

    3 details in Everything

82. 2.6.0 Aug 17, 2023 · release notes

    Bytebase 2.6.0 adds LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. support, RisingWave database instance type, and multiple read-only data sources.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.6.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.6.0

    └──▷ HOW TO FIND IT
    Configure LDAP as the SSO provider in Bytebase administration.
    📍See: https://www.bytebase.com/docs/administration/sso/ldap/
    • Supports using LDAP for configuring SSO

    1 detail in Everything

83. 2.5.0 Aug 3, 2023 · release notes

    Bytebase 2.5.0 adds Azure DevOps VCSVCSVersion control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. integration, Sign-in Frequency settings, and DB change history export.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.5.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.5.0

    • Adds Azure DevOps as a supported VCS integration provider.
    • Adds Sign-in Frequency configuration for authentication policies.
    • Enables exporting changes from the database change history view.
    • Introduces Schema Designer support for MySQL databases.
    • Adds column template definition capability within Schema Designer.

    5 details in Everything

84. 2.4.1 Jul 20, 2023 · release notes

    Bytebase 2.4.1 adds GitHub Enterprise integration, XLSX exports, Oracle schema management, and a new --disable-sample flag.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.4.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.4.1

    • Supports exporting data as XLSX file format.

    1 detail in Everything

85. 2.4.0 Jul 6, 2023 · release notes

    Bytebase 2.4.0 adds workspace-level data access control, Snowflake/Redshift deep support, and DML export.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.4.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.4.0

    • Supports workspace-level data access control for query and export with custom approval workflows
    • Adds support for Snowflake Task and Stream objects alongside data access control
    • Enables Redshift datashare query, data access control, and data anonymization
    • Allows exporting data as DML scripts instead of standard CSV/SQL formats
    • Permits markdown formatting in Issue comments

    5 details in Everything

86. 2.3.0 Jun 21, 2023 · release notes

    Bytebase 2.3.0 adds Snowflake SQL review rules, a global Export Center for data downloads, Oracle anonymization, and external approval nodes

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.3.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.3.0

    └──▷ HOW TO FIND IT
    Review SQL for Snowflake-specific rules.
    📍# Access the SQL Review feature for a Snowflake instance via the Bytebase UI
    Download exported data from the centralized Export Center.
    📍# Navigate to the Export Center in the Bytebase console to manage and download data exports.
    Configure an external node in a custom approval flow.
    📍# Add an External Approval Node to your custom approval workflow settings.
    • SQL Review with support for Snowflake databases.
    • Export Center for centralized data export management.
    • Anonymize data capability for Oracle databases.
    • Configure External Approval Nodes in custom approval flows.

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Project's Tenant Mode is renamed to Batch Mode.
87. 2.2.0 Jun 9, 2023 · release notes

    Bytebase 2.2.0 adds batch change by database groups and table-level data query requests.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.2.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.2.0

    • Supports batch change by database groups in tenant projects.
    • Supports table-level data query requests for applying for the querier role.

    2 details in Everything

88. 2.1.0 May 26, 2023 · release notes

    Bytebase 2.1.0 adds Data Query/Export approval flows, SSH tunneling for Postgres/Redis, and Oracle SQL Review.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.1.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.1.0

    • Adds Data Query approval flow to gate raw data access requests.
    • Adds Data Export approval flow to control bulk data extraction.
    • Supports SSH tunneling for PostgreSQL connections from the tool.
    • Supports SSH tunneling for Redis connections from the tool.
    • Enables SQL Review rules specifically for Oracle database schemas.

    5 details in Everything

89. 2.0.0 May 11, 2023 · release notes

    Bytebase 2.0 introduces AI index advisor, SSH database connections, secret variables, MyBatis SQL review, and OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. cert skip option

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 2.0.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 2.0.0

    • skip.verify.server.cert option added to disable server certificate verification for SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. OIDC connections
    • Database-level secret variables supported for injection into SQL change workflows
    • MyBatis 3 XML mapper files now reviewed during GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. CI workflows

    3 details in Everything

90. 1.17.0 Apr 27, 2023 · release notes

    Bytebase 1.17 adds slow query display for MySQL/Postgres, weekly email summaries, multi-target schema sync, and custom roles.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.17.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.17.0

    • Adds display of slow queries for MySQL and PostgreSQL databases
    • Adds weekly slow query summary emails sent to administrators
    • Enables syncing schema changes to multiple target databases simultaneously
    • Adds the ability to configure custom roles for projects

    4 details in Everything

91. 1.16.0 Apr 13, 2023 · release notes

    Bytebase 1.16 adds 2FA enforcement and new database support with enhanced UI controls

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.16.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.16.0

    └──▷ HOW TO FIND IT
    Enforce 2FA for all team members via the UI
    📍Go to Administration › Security › Authentication and enable 'Require two-factor authentication (2FA) for all users'
    Create a new connection to an Oracle database instance
    📍Click New Connection in the database list, select Oracle from the Type dropdown, and enter your host/port/credentials
    • Enforces two-factor authentication for all users via the Require two-factor authentication (2FA) for all users configuration option in Administration settings
    • Supports Oracle, MSSQL & MariaDB databases as new connection targets in the database list
    • Adds UI control to skip all failed tasks in the current stage of an issue during execution

    3 details in Everything

92. 1.15.0 Apr 11, 2023 · release notes

    Bytebase adds Bitbucket Cloud support for GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. and PostgreSQL view dependency checks in SQL Review

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.15.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.15.0

    • Adds bitbucket.org as a supported Git provider for GitOps workflows
    • Enables PostgreSQL view dependency checking within the existing SQL Review engine

    2 details in Everything

93. 1.14.0 Mar 20, 2023 · release notes

    Bytebase 1.14.0 adds ChatSQL natural language queries, 2FA login support, Redis integration, and state-based migration for MySQL.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.14.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.14.0

    • Adds ChatSQL feature to convert natural language prompts into SQL queries using OpenAI
    • Adds Two-Factor Authentication (2FA) support for user login
    • Adds State-based Migration capability for MySQL databases in Beta

    3 details in Everything

94. 1.13.0 Mar 3, 2023 · release notes

    Bytebase 1.13.0 adds MySQL DML rollback generation, OIDCOIDCOpenID Connect, a sign-in protocol built on OAuth 2.0. An application uses identity information from a trusted provider instead of maintaining a separate password for each user. SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. support, and GitLab.com to its GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. workflow.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.13.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.13.0

    └──▷ HOW TO FIND IT
    Generate rollback SQL for MySQL DML changes directly within the application.
    📍Navigate to Change Database › Rollback Data Changes and select the MySQL target to generate rollback statements.
    Configure OIDC for SSO access in the administration settings.
    📍Go to Administration › Security › Single Sign-On and enable the OIDC provider configuration.
    • Adds Generate SQL statements to rollback DML for MySQL capability
    • Supports Single Sign-On (SSO) with OIDC
    • GitOps workflow now supports GitLab.com as a VCSVCSVersion control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. provider alongside GitHub.com and GitLab self-hosted

    3 details in Everything

95. 1.12.1 Feb 19, 2023 · release notes

    Bytebase v1.12.1 adds OAuth 2.0OAuth 2.0An open authorization framework (IETF RFC 6749) that lets a service grant limited API access to a third party without sharing credentials, giving cyber tools a standard way to authenticate against external platforms. SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management., Spanner support, and Terraform MySQL role CRUDCRUDThe four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.12.1 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.12.1

    • Adds OAuth 2OAuth 2An open authorization framework (RFC 6749) that lets a service grant limited access to a user's resources on another service without exposing credentials, giving cyber tools a standard way to authenticate against third-party APIs..0 support for Single Sign-On (SSO) configuration.
    • Enables change and query operations for Google Cloud Spanner databases.
    • Allows the Terraform Bytebase provider to perform Create, Read, Update, and Delete (CRUD) actions on MySQL roles.
    • Masks sensitive fields in PostgreSQL query results.

    4 details in Everything

96. 1.12.0 Feb 7, 2023 · release notes

    Bytebase 1.12 adds Terraform policy resource and PostgreSQL SQL Review rules

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.12.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.12.0

    └──▷ USE IT
    Configure the specific resource in your Terraform code to apply policies to your database environments
    hcl copy

    resource "bytebase_policy" "example" {
      name = "my-policy"
      # ... policy configuration arguments
    }

97. 1.11.0 Jan 21, 2023 · release notes

    Bytebase 1.11.0 adds MongoDB support, Schema Diagram, Schema Editor for PostgreSQL, stage-change webhooks, and SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. connections.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.11.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.11.0

    └──▷ HOW TO FIND IT
    View the ER diagram for a database schema using the new Schema Diagram feature in the Bytebase console.
    📍In the console, go to Database › Schema Diagram
    Edit PostgreSQL schema directly via the UI-based Schema Editor for a specific project.
    📍In the console, go to Database › Schema Editor for the target database
    Configure Webhook notifications to fire when a stage status changes in a project.
    📍In the console, go to Project Settings › Webhook Integration and enable stage change notifications
    • Adds MongoDB database support as a new platform
    • Adds Schema Diagram feature to view Entity-Relationship diagrams in the UI
    • Adds Schema Editor for editing PostgreSQL schema via the UI
    • Adds webhook notifications on stage status changes
    • Adds project view to SQL Editor's database tree for navigation

    +2 more show less

    • Displays inactive rules in the Access Control rule list
    • Supports PostgreSQL SSL connections

    7 details in Everything

98. 1.10.0 Dec 29, 2022 · release notes

    Bytebase v1.10 adds PostgreSQL role CRUDCRUDThe four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information. via Terraform, MySQL PK/FK editing, SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. support, and tenant-mode online migration.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.10.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.10.0

    • Workspace owner and DBA can now view audit logs
    • Support CRUD database role (only for PostgreSQL) via Terraform Provider
    • Support viewing and editing primary keys and foreign keys in the Schema Editor for MySQL
    • Support MySQL/TiDB SSL connection
    • Support DML with large SQL (up to 100MB)

    +1 more show less

    • Support online migration for UI workflow with tenant-mode

    6 details in Everything

99. 1.9.0 Dec 19, 2022 · release notes

    Bytebase 1.9.0 adds Terraform provider support for environments and instances, plus PostgreSQL schema sync and MySQL column masking.

    └──▷ GET THIS VERSION

    copy

    $ git clone --branch 1.9.0 https://github.com/bytebase/bytebase.git
    # already have the repo? check out this version:
    $ git checkout 1.9.0

    • Adds beta support for synchronizing schema for PostgreSQL (Schema, Table, Index, Constraint, Sequence)
    • Adds support for masking column-level sensitive data for MySQL
    • Introduces a new UI for Admin mode of SQL Editor

    3 details in Everything

100. 1.8.0 Dec 19, 2022 · release notes

     Bytebase 1.8.0 adds MySQL schema sync, Lark issue approval, SQL Review CI in GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control., admin mode SQL execution, and multi-database alter on tenant mode.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.8.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.8.0

     • MySQL schema syncing is now supported for data sources.
     • Issues can be approved via the Lark (Feishu) integration.
     • SQL Review CI can be run as part of the GitOps workflow.
     • Admin-mode SQL execution is available in the SQL Editor for DBAs and workspace owners.
     • Multiple databases can be altered simultaneously in tenant mode.

     5 details in Everything

101. 1.6.0 Dec 19, 2022 · release notes

     Bytebase v1.6.0 adds read-only data source support for read-replica instances

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.6.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.6.0

102. 1.4.0 Dec 19, 2022 · release notes

     Bytebase 1.4.0 adds AWS S3 backup storage and new CLI flags for external URL configuration.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.4.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.4.0

     • --external-url startup flag replaces --host to configure the externally visible URL.
     • AWS S3 is now supported as a backup storage backend.
     • Support added for DDL/DML aliasing in GitOpsGitOpsA practice where Git repositories serve as the single source of truth for infrastructure and application state, with automated systems continuously reconciling live environments to match what is declared in version control. name templates.

     3 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !The --host startup option has been removed and replaced by --external-url.
103. 1.9.1 Dec 19, 2022 · release notes

     Bytebase 1.9.1 adds MySQL Schema Editor, MySQL data masking for all queries, and Terraform resource management.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.9.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.9.1

     └──▷ USE IT
     Manage a Bytebase instance via Terraform by adding a new resource block using the newly supported bytebase_instance resource.
     hcl copy

     resource "bytebase_instance" "example" {
       name = "my-mysql-instance"
       # ... configuration details
     }

     Apply data masking policies that now cover all query types in MySQL, ensuring sensitive columns are anonymized regardless of the SQL operation performed.
     📍https://www.bytebase.com/docs/administration/anonymize-data
     • Instance and Environment resources are now supported in the Terraform Bytebase Provider, allowing infrastructure-as-code management of these entities
     • Schema Editor is now available for MySQL databases, enabling visual schema changes directly within the platform
     • Data masking for MySQL databases now supports all query types, extending anonymization coverage beyond previous limitations
     • Schema Sync for PostgreSQL adds support for Enum Type, Function, Trigger, and Extension objects
     • Database tenant labels now accept arbitrary string values without requiring pre-definition in the system

     5 details in Everything

104. 1.7.0 Oct 27, 2022 · release notes

     Bytebase 1.7.0 adds 31 MySQL review rules and DDL validation in SQL review

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.7.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.7.0

     • Adds 31 new review rules for MySQL databases to catch common anti-patterns and enforce standards automatically.
     • Enables DDL validation within the SQL review workflow, preventing schema changes that violate structural constraints before they reach production.

     2 details in Everything

105. 1.5.0 Sep 29, 2022 · release notes

     Bytebase 1.5.0 adds LGTM issue inspection, disallow commit MySQL rule, one-click backup disable, and PITR task checks.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.5.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.5.0

     • LGTM inspection for issues allows multiple members to review the same issue
     • disallow commit SQL review rule for MySQL disallows commit in SQL statements if enabled
     • Support one-click to disable the automatic backup policy for all databases in one environment
     • Task checks for PITR issues

     4 details in Everything

106. 1.3.2 Sep 1, 2022 · release notes

     Bytebase 1.3.2 adds PostgreSQL Explain Visualizer, MySQL PITR, env protection badges, and debug log export.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.3.2 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.3.2

     • Integrate PostgreSQL Explain Visualizer to allow users to visualize EXPLAIN plan outputs directly within the application.
     • Support in-place backup restore for PostgreSQL enabling restoration of backups directly over existing databases without manual setup.
     • Support PITR to a new database for MySQL allowing Point-in-Time Recovery operations targeting a newly created database instance.
     • Users can mark an environment as 'protected' to enforce access controls, indicated by a shield badge in the UI.

     4 details in Everything

107. 1.3.1 Aug 18, 2022 · release notes

     Bytebase 1.3.1 adds SQL Review GitHub Action integration and project owner approvers.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.3.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.3.1

     └──▷ HOW TO FIND IT
     Automate SQL review in CI by running the new GitHub Action on a pull request.
     📍steps: - uses: actions/checkout@v3 - name: SQL Review uses: Bytebase/sql-review-action@latest
     Grant a project owner approval rights to schema changes in an issue.
     📍1. Open the project Settings 2. Navigate to the Approvers tab 3. Add the desired Project Owner as an Issue approver
     • SQL Review GitHub Action is now available on the GitHub Action Marketplace for automating database schema reviews
     • Project owners can be assigned as Issue approvers to control change approval workflows
     • Issue comment area adds an LGTM button for quick approval actions

     3 details in Everything

108. 1.3.0 Aug 4, 2022 · release notes

     Bytebase 1.3.0 adds PostgreSQL SQL review with 13 rules, GitHub VCSVCSVersion control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. integration, and point-in-time database restore.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.3.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.3.0

     └──▷ HOW TO FIND IT
     Review PostgreSQL queries against built-in rules before applying migrations.
     📍N/A (Feature requires UI/Backend interaction not exposed via CLI/API in notes)
     Enable GitHub.com as an authentication provider for the cyber tooling.
     📍N/A (Feature requires UI/Backend interaction not exposed via CLI/API in notes)
     Restore a database to a specific point in time before the last migration.
     📍N/A (Feature requires UI/Backend interaction not exposed via CLI/API in notes)
     • Adds PostgreSQL SQL review capability with 13 built-in rules
     • Adds GitHub.com as a supported VCS integration and authentication provider
     • Enables one-click database restore to the time point before the last migration
     • Adds configurable 'day of the week' and backup retention period settings for database backups
     • Adds support for multi-selection when transferring databases into a project

     +2 more show less

     • Adds Upload SQL option when editing an issue's SQL statement
     • Supports database level schema sync

     7 details in Everything

109. 1.2.2 Jul 21, 2022 · release notes

     Bytebase 1.2.2 adds gh-ost online migration support and new SQL Review rules for foreign keys and table drop naming

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.2.2 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.2.2

     • Adds gh-ost as a supported engine for online schema migration on large tables (Beta)
     • Adds a new SQL Review rule to disallow foreign keys on a table (table-no-fk)
     • Adds a new SQL Review rule for naming convention when dropping a table (table-drop-naming)
     • [SQL Advise API] Enable database connection

     4 details in Everything

110. 1.2.1 Jul 7, 2022 · release notes

     Bytebase 1.2.1 adds in-place Point-in-time Recovery (preview), ClickHouse cluster support, and the GET /v1/sql/advise API

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.2.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.2.1

     └──▷ USE IT
     Send a SQL statement to the API to receive optimization advice before running it.
     shell copy

     curl -H "Content-Type: application/json" http://localhost:8080/v1/sql/advise -d '{"sql": "SELECT * FROM users"}'

     • GET /v1/sql/advise OpenAPIOpenAPIA vendor-neutral specification for describing REST APIs in a machine-readable format, maintained by the OpenAPI Initiative. Cyber tools use it to auto-generate clients, documentation, and validation from a single source of truth. endpoint for SQL analysis.
     • Cluster support when creating ClickHouse databases.

     2 details in Everything

111. 1.2.0 Jun 23, 2022 · release notes

     Adds schema review policy enforcement to SQL Editor with configurable error/warning levels

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.2.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.2.0

     └──▷ HOW TO FIND IT
     When you want to strictly enforce SQL compliance and prevent non-compliant queries from running against the database.
     📍In the SQL Editor, set a rule's level to Error; executing violating SQL will be blocked with an error message.
     When you want to review SQL for compliance without blocking execution, using warnings instead of errors.
     📍In the schema review policy settings, change a rule's level from Error to Warning; violating SQL will display a warning but continue running.
     • Schema Review policy in SQL Editor now blocks execution and shows errors when rules are violated
     • Support for changing rule level from Error to Warning within the schema review policy

     2 details in Everything

112. 1.1.1 Jun 10, 2022 · release notes

     Bytebase 1.1.1 adds schema review policy configuration for environments.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.1.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.1.1

     • Adds archive checkers for environment/project/instance

     1 detail in Everything

113. 1.1.0 May 26, 2022 · release notes

     Bytebase 1.1.0 adds VCSVCSVersion control system: software that tracks changes to files over time, letting teams collaborate and roll back mistakes. Cyber tools use it to manage source code, configs, and signatures. SQL sync in SQL Editor, sheet starring, PostgreSQL extension listing, and Postgres owner creation.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.1.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.1.0

     • List database extensions for PostgreSQL support
     • Support creating a Postgres database with an owner
     • Star the sheets to save them in a list
     • Sync your SQL scripts stored in the linked VCS system in SQL Editor

     4 details in Everything

114. 1.0.5 May 12, 2022 · release notes

     Adds custom project webhook support for Bytebase v1.0.5

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.0.5 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.0.5

     • Adds the ability to configure a custom HTTP webhook at the project level to receive notifications on schema change events.
     • Adds a Sync schema afterward checkbox on instance create and detail pages to disable automatic database sync.

     2 details in Everything

115. 1.0.4 Apr 28, 2022 · release notes

     Bytebase 1.0.4 adds --dsn CLI flag, installation script, sheet management dashboard, and /healthz endpoint.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.0.4 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.0.4

     • Supports --dsn option in the Bytebase CLI
     • Adds a dashboard page to manage all sheets
     • Allows owner and DBA to view all projects under Settings
     • Adds /healthz health check endpoint

     4 details in Everything

116. 1.0.3 Apr 14, 2022 · release notes

     Bytebase 1.0.3 adds runtime Debug mode toggle and EXPLAIN query support in the SQL editor.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.0.3 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.0.3

     • Adds a Toggle Debug mode option for easier troubleshooting
     • [SQL editor] supports more types of EXPLAIN queries on the basis of EXPLAIN SELECT, such as EXPLAIN INSERT

     2 details in Everything

117. 1.0.2 Mar 31, 2022 · release notes

     Bytebase 1.0.2 adds branding customization for Team/Enterprise plans and SQL Editor enhancements.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.0.2 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.0.2

     • Adds support for branding customization, available in Team/Enterprise Plan.
     • [SQL Editor] Highlights the editing SQL query block for easier identification.
     • [SQL Editor] Adds a button to format SQL queries directly within the editor.

     3 details in Everything

118. 1.0.1 Mar 14, 2022 · release notes

     Bytebase 1.0.1 adds instance read-only connection and tenant mode DML support

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.0.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.0.1

     • support_instance_read_only_connection enables a dedicated read-only user for database queries in SQL Editor and other read-only scenarios.
     • [Tenant Mode] Enable Data Change (DML) for tenant mode projects

     2 details in Everything

119. 1.0.0 Mar 8, 2022 · release notes

     Bytebase 1.0.0 adds Role-Based-Access-Control (RBACRBACRole-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists.), GitLab login, and SQL backward compatibility checks.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 1.0.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 1.0.0

     • Adds Role-Based-Access-Control (RBAC) with Owner, DBA, and Developer roles to control collaboration during database development.
     • Adds GitLab login support for authentication.
     • Adds SQL backward compatibility check and schema drift detection capabilities.
     • Adds per-environment schema review and backup policy configuration.

     4 details in Everything

120. 0.13.0 Feb 17, 2022 · release notes

     Bytebase 0.13.0 adds SQL editor sheet sharing and saves Remodel queries as sheets

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.13.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.13.0

     • SQL editor now supports sheet sharing, allowing collaborators to view or edit shared SQL scripts.
     • Remodel queries are saved as sheets, enabling versioned management of schema changes within the Sheet interface.

     2 details in Everything

121. 0.12.0 Jan 20, 2022 · release notes

     Bytebase 0.12.0 adds multi-tenancy management, GitLab signup/login, DML workflows, and SQL editor tabs.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.12.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.12.0

     • Adds Signup and login via GitLab EE/CE authentication provider
     • Introduces Data change (DML) workflow for managing data modifications
     • Enables creating and managing database labels to identify tenants in multi-tenancy setups

     3 details in Everything

122. 0.11.0 Jan 6, 2022 · release notes

     Bytebase 0.11.0 introduces a preview SQL Editor with auto-complete, query execution, and PR preview environments

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.11.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.11.0

     └──▷ HOW TO FIND IT
     Execute a SELECT query and view results directly in the Bytebase UI during a PR review.
     📍Open PR Preview Environment -> SQL Editor tab -> Run SELECT * FROM users LIMIT 10
     Use auto-complete in the new SQL Editor to write complex queries with table schema visibility.
     📍SQL Editor -> Type SELE (auto-complete triggers) -> View schema in bottom left panel
     • SQL Editor preview feature allows running SELECT queries and displaying results in a table view within the UI.
     • SQL Editor provides auto-complete and context menu support for database connections.
     • Preview environment is now available for each pull request to test schema changes before merging.

     3 details in Everything

123. 0.10.0 Dec 24, 2021 · release notes

     Bytebase 0.10.0 adds Chinese UI localization, earliest execution time constraints, SQL change audit logging, and detailed check status modals.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.10.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.10.0

     • Adds zh-CN Chinese language support to the UI via a new locale option
     • Adds earliest_allowed_time constraint to task execution for scheduling control
     • Introduces a detailed check status modal in the UI for granular validation feedback

     3 details in Everything

124. 0.9.0 Dec 9, 2021 · release notes

     Bytebase 0.9.0 adds cmd+k command bar, database webhooks, and Gitpod preview

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.9.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.9.0

     └──▷ HOW TO FIND IT
     Quickly open a specific page or action via keyboard shortcut
     📍Press cmd+k (or ctrl+k on Windows/Linux) in the Bytebase UI to open the command palette
     Configure a webhook to receive notifications when database schema changes occur
     📍In the project settings, go to Integrations › Webhooks and add your desired database webhook URL
     • Adds cmd+k command bar experience for rapid navigation and action execution
     • Adds database webhook support to trigger external events on database changes
     • Adds Gitpod Code Preview integration for reviewing code within the GitPod IDE

     3 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !Upgrading to 0.9.0 involves breaking schema changes that require manual migration assistance from support@bytebase.com
125. 0.8.1 Nov 15, 2021 · release notes

     Bytebase 0.8.1 introduces a new onboarding wizard and updated UI for sign-in and error pages.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.8.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.8.1

     • Adds a new wizard on the home page to guide users through initial setup.

     1 detail in Everything

126. 0.8.0 Nov 10, 2021 · release notes

     Bytebase 0.8.0 adds Snowflake support for database migration management

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.8.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.8.0

     • Adds Snowflake as a supported database platform for migrations

     1 detail in Everything

     └──▷ BREAKING ON UPGRADE

     • !Schema changes require manual upgrade assistance from support@bytebase.com when upgrading from previous versions
127. 0.7.2 Oct 25, 2021 · release notes

     Bytebase 0.7.2 adds ClickHouse support

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.7.2 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.7.2

128. 0.7.0 Oct 8, 2021 · release notes

     Bytebase 0.7.0 adds PostgreSQL support, anomaly center, and migration diff capabilities

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.7.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.7.0

     • Adds PostgreSQL database support for schema management and migrations
     • Enables Side-by-side migration version diffing in the UI
     • Adds Backup schedule environment policy configuration options

     3 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !The release includes breaking schema changes that require manual intervention via support@bytebase.com for upgrades from previous versions
129. 0.6.0 Sep 18, 2021 · release notes

     Bytebase 0.6.0 adds TiDB support and task check enforcement for schema updates

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.6.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.6.0

     • Adds TiDB database support
     • Adds task check enforcement that blocks schema update tasks failing syntax or db connection checks

     2 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !Upgrading from a previous version requires manual migration assistance from support; the release notes indicate breaking schema changes but do not specify the exact renamed/removed fields or flags.
130. 0.5.0 Sep 9, 2021 · release notes

     Bytebase 0.5.0 adds version control workflow path templates and dedicated migration history page

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.5.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.5.0

     └──▷ HOW TO FIND IT
     Configure where migration files are stored in your version control system.
     📍Specify the migration file path template in the Version Control Workflow settings.
     Automatically update a specific file with the latest schema after each successful migration.
     📍Specify the schema path template in the Version Control Workflow settings.
     • Allow user to specify the migration file path template for Version Control Workflow based workflow.
     • Allow user to specify the schema path template for Version Control Workflow; Bytebase updates the latest schema to this path after each migration.
     • Record schema snapshot in the migration history.

     3 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !Schema change is not backward compatible; upgrade from previous version requires manual intervention via support@bytebase.com.
131. 0.4.1 Aug 31, 2021 · release notes

     Bytebase 0.4.1 introduces UI-based SQL rollback and new database detail page actions

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.4.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.4.1

     └──▷ HOW TO FIND IT
     Reverse a deployed SQL migration via the web interface without using CLI or direct DB access.
     📍Open the SQL review workflow in the Bytebase UI and select Rollback for the relevant change.
     • Supports rollback of SQL changes directly within the UI-based SQL review workflow

     1 detail in Everything

132. 0.4.0 Aug 19, 2021 · release notes

     Adds per-database backup/restore, automatic weekly backups, and multi-platform webhook integrations.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.4.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.4.0

     • Weekly automatic backup schedules per-database backups without manual intervention
     • Manual backup triggers on-demand database snapshots
     • Database restore supports restoring a backup to a different database target
     • Webhook endpoints for Slack, Discord, Teams, DingTalk, Feishu, and WeCom enable notifications on issue creation, status changes, task status changes, info updates, and comment creation

     4 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !The schema undergoes a breaking change; upgrading from a previous version requires manual migration assistance from support@bytebase.com.
133. 0.3.0 Aug 2, 2021 · release notes

     Bytebase v0.3.0 adds environment approval policies, inbox notifications, and database instance user sync.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.3.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.3.0

     • Adds Environment approval policy for controlling deployment workflows
     • Introduces an Inbox UI component for notifications
     • Adds Database instance user sync capability to keep instance users in check

     3 details in Everything

134. 0.2.1 Jul 24, 2021 · release notes

     Bytebase 0.2.1 adds external SQL console configuration and new issue list view grouping.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.2.1 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.2.1

     • Allows configuring an external SQL console (e.g., phpMyAdmin) via settings guide
     • Adds an issue list view with different grouping forms
     • Introduces new custom 403 and 404 error pages

     3 details in Everything

135. 0.2.0 Jul 19, 2021 · release notes

     Bytebase 0.2.0 adds Migration History and Table Detail views

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.2.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.2.0

     • Adds Migration History under database detail view to track schema changes
     • Adds table detail view for basic table info, column info, and index info

     2 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !Breaking schema change required; manual upgrade via support@bytebase.com is needed for upgrades from 0.1.0
136. 0.1.0 Jul 9, 2021 · release notes

     First open source release of Bytebase with initial Docker deployment support.

     └──▷ GET THIS VERSION

     copy

     $ git clone --branch 0.1.0 https://github.com/bytebase/bytebase.git
     # already have the repo? check out this version:
     $ git checkout 0.1.0

     └──▷ USE IT
     Deploy the initial version of Bytebase locally using Docker for immediate access to database management.
     shell copy

     docker run --init --name bytebase --restart always --publish 8080:8080 --volume ~/.bytebase/data:/var/opt/bytebase bytebase/bytebase:0.1.0 --data /var/opt/bytebase --host http://localhost --port 8080

     • Adds docker run command to deploy Bytebase v0.1.0 on localhost:8080

     1 detail in Everything