<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>bytebase — The Cyber Toolchain</title>
    <link>https://cybertoolchain.io/tools/bytebase</link>
    <description>New releases and features in bytebase, tracked by The Cyber Toolchain.</description>
    <language>en</language>
    <lastBuildDate>Fri, 30 Oct 2026 07:56:24 GMT</lastBuildDate>
    <atom:link href="https://cybertoolchain.io/tools/bytebase/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>bytebase 1.0.0</title>
      <link>https://api.bytebase.com/openapi.yaml</link>
      <guid isPermaLink="true">https://api.bytebase.com/openapi.yaml</guid>
      <pubDate>Fri, 30 Oct 2026 07:56:24 GMT</pubDate>
      <description>API surface changed: +1 endpoint, 18 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• New endpoint POST /v1/databases:search⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.24.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.24.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.24.0</guid>
      <pubDate>Thu, 22 Oct 2026 16:38:22 GMT</pubDate>
      <description>Bytebase 3.24.0 adds MCP read-write agent workflows, BigQuery SQL review, and self-hosted admin recovery without downtime.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds `release` and `has_release` filter parameters to `ListPlans` API, plus `task_status` filter, so GitOps plans can be distinguished from console-created plans.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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&apos;s own permissions.
• Adds BigQuery SQL review support with two rules: &apos;Enforce the presence of WHERE condition in UPDATE/DELETE statements&apos; and &apos;Restrict the SQL file size&apos;.
• Adds self-hosted admin recovery: re-enable password sign-in or reset a user&apos;s password while Bytebase keeps running, with no restart required, scriptable for unattended use.
• Adds TLS enforcement for SQL Server and Oracle connections: &apos;Verify server certificate&apos; 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).
• Adds a setup wizard for new workspaces, guiding through naming, project creation with a sample or real database, and team setup.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 1.0.0</title>
      <link>https://api.bytebase.com/openapi.yaml</link>
      <guid isPermaLink="true">https://api.bytebase.com/openapi.yaml</guid>
      <pubDate>Sat, 17 Oct 2026 08:03:27 GMT</pubDate>
      <description>API surface changed: +1 endpoint, 2 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• New endpoint GET /v1/projects/{project}/issues/{issue}/reviewRuns/{reviewRun}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 1.0.0</title>
      <link>https://api.bytebase.com/openapi.yaml</link>
      <guid isPermaLink="true">https://api.bytebase.com/openapi.yaml</guid>
      <pubDate>Tue, 13 Oct 2026 13:58:07 GMT</pubDate>
      <description>API surface changed: 4 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.23.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.23.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.23.0</guid>
      <pubDate>Thu, 24 Sep 2026 19:58:20 GMT</pubDate>
      <description>Bytebase 3.23.0 adds MCP access policies, inline plan-review comments, any-OIDC workload identities, and a query-plan visualizer in SQL Editor.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• 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 = &quot;OIDC&quot;` 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.
• Adds MCP access policy control under **Integration** &gt; **MCP** &gt; **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 JWKS 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.
Breaking changes:
• `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 == &apos;users/bb@bytebase.com&apos;` to `actor == &apos;users/bb@bytebase.com&apos;`.
• `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&apos;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 token 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 providers now requires authentication; unauthenticated calls will be rejected.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 1.0.0</title>
      <link>https://api.bytebase.com/openapi.yaml</link>
      <guid isPermaLink="true">https://api.bytebase.com/openapi.yaml</guid>
      <pubDate>Wed, 23 Sep 2026 13:23:52 GMT</pubDate>
      <description>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.
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.22.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.22.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.22.1</guid>
      <pubDate>Thu, 10 Sep 2026 19:46:39 GMT</pubDate>
      <description>Bytebase 3.22.1 adds GPT-5 model support and improves service account search in Grant Access.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Supports GPT-5 models for AI features alongside existing GPT-4o support.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.22.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.22.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.22.0</guid>
      <pubDate>Fri, 28 Aug 2026 08:18:26 GMT</pubDate>
      <description>Bytebase 3.22.0 adds project-scoped instances, Data Explorer, login lockout, new `bytebase recovery` CLI, and per-object saved-query sharing.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
• Adds `bytebase recovery` CLI command as a break-glass path to re-enable password sign-in or reset a user&apos;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 IAM 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.
• 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 MFA 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.
Breaking changes:
• `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 JIT access-grant exports or synchronous SQL Editor export.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.19.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.19.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.19.1</guid>
      <pubDate>Thu, 18 Jun 2026 14:08:31 GMT</pubDate>
      <description>StarRocks parser support and shareable SQL Editor query history URLs
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.19.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.19.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.19.0</guid>
      <pubDate>Fri, 05 Jun 2026 15:37:35 GMT</pubDate>
      <description>Bytebase 3.19 adds just-in-time data export approval flows and active VCS user tracking for GitOps
• 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
Breaking changes:
• `bytebase-action check` and `bytebase-action rollout` now fail with an error (previously a warning) when the action version is outside the compatibility window
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.18.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.18.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.18.1</guid>
      <pubDate>Mon, 01 Jun 2026 09:35:32 GMT</pubDate>
      <description>Bytebase 3.18.1 adds PostgreSQL 18 support, MCP OAuth for SaaS, and removes the --demo flag
• Adds support for PostgreSQL 18 with recognition of built-ins like uuidv7() in SQL analysis and schema diff.
• Enables automatic MCP 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.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.18.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.18.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.18.0</guid>
      <pubDate>Thu, 14 May 2026 14:17:06 GMT</pubDate>
      <description>Bytebase 3.18 adds Google Chat webhook, AWS RDS IAM auth, MariaDB DML rollback, and `--custom-header` CLI flag.
• `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
• 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
Breaking changes:
• The `require_2fa` field on `WorkspaceProfileSetting` is renamed to `require_mfa`; callers updating workspace profile settings via `SettingService.UpdateSetting` must update their config or IaC 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.17.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.17.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.17.1</guid>
      <pubDate>Thu, 23 Apr 2026 09:08:44 GMT</pubDate>
      <description>Bytebase 3.17.1 adds instance TLS modes and Oracle/PG/MySQL/MSSQL SQL review rules
• Adds `Disabled`, `TLS`, and `Mutual TLS` 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.17.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.17.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.17.0</guid>
      <pubDate>Thu, 09 Apr 2026 14:53:18 GMT</pubDate>
      <description>Bytebase 3.17.0 adds HA support, Page Agent AI assistant, MCP `query_database` tool, and CosmosDB local emulator.
• Supports licensed multi-replica deployments with shared external PostgreSQL metadata for High Availability
• Adds in-app `Page Agent` with threaded resumable conversations, DOM-aware autocomplete, and tool-calling
• 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
• 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
Breaking changes:
• `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/-`
• CEL filter substring-search syntax changed from matches() to contains() across plan, database, instance, project, group, user, service account, workload identity, 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.16.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.16.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.16.1</guid>
      <pubDate>Thu, 26 Mar 2026 08:38:11 GMT</pubDate>
      <description>Bytebase 3.16.1 adds fast-follow refresh mode for rollout status and improved CosmosDB SQL editor query support
• Adds `fast-follow` refresh mode so rollout status updates more quickly after user actions
• Expands supported query syntax for CosmosDB in the SQL editor
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.16.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.16.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.16.0</guid>
      <pubDate>Thu, 12 Mar 2026 10:47:56 GMT</pubDate>
      <description>Bytebase 3.16 adds JIT data access approval, GitOps landing page, dynamic masking for MongoDB/Elasticsearch, and workload identity federation.
• 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
• 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 BigQuery &amp; Spanner
• Adds ROW STORE COMPRESS syntax support for Oracle databases
• Adds `search_path` resolution via current user for PostgreSQL databases
Breaking changes:
• 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 UUID strings, invalidating previously bookmarked integer IDs
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.15.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.15.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.15.1</guid>
      <pubDate>Thu, 26 Feb 2026 12:03:21 GMT</pubDate>
      <description>Bytebase 3.15.1 adds a dedicated SQL Editor Read User role for SELECT/EXPLAIN/INFO-only access.
• Enforces `bb.issues.update` permission requirement when editing issues, removing the implicit creator-can-always-edit exception.
Breaking changes:
• Issue creators who previously could edit their own issues without `bb.issues.update` will now be denied unless that permission is explicitly granted.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.15.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.15.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.15.0</guid>
      <pubDate>Thu, 12 Feb 2026 15:46:08 GMT</pubDate>
      <description>Bytebase 3.15 introduces project-level service accounts, workload identities, and MongoDB statement-type access control in SQL Editor
• Adds `ServiceAccountService` and `WorkloadIdentityService` APIs for managing machine identities at the project level
• Adds `workloadIdentity:{email}` IAM 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
Breaking changes:
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.14.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.14.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.14.1</guid>
      <pubDate>Thu, 29 Jan 2026 10:09:57 GMT</pubDate>
      <description>Bytebase 3.14.1 adds Google Cloud SQL IAM authentication support and improves result masking performance.
• Adds `Google Cloud SQL` IAM authentication support for database connections
• Improves result masking performance for queries spanning multiple databases and enhances masking coverage
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.14.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.14.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.14.0</guid>
      <pubDate>Thu, 15 Jan 2026 10:18:13 GMT</pubDate>
      <description>Bytebase v3.14 introduces refresh tokens, granular masking/exemption policies, Terraform project settings, and Workload Identity support.
• 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
• Supports Workload Identity authentication with GitLab CI for user groups
Breaking changes:
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.13.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.13.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.13.0</guid>
      <pubDate>Thu, 18 Dec 2025 08:34:10 GMT</pubDate>
      <description>Bytebase 3.13.0 adds MCP integration, Workload Identity for OIDC/GitHub Actions, and Microsoft Teams direct messages.
• 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 CEL 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.
• 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/SSL 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.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.12.2</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.12.2</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.12.2</guid>
      <pubDate>Thu, 04 Dec 2025 09:24:38 GMT</pubDate>
      <description>Bytebase 3.12.2 adds visualized EXPLAIN support for SQL Server and improves Doris syntax compatibility.
• **SQL Server** - Add visualized EXPLAIN support in SQL Editor
• **Doris** - Improve syntax compatibility
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.12.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.12.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.12.1</guid>
      <pubDate>Thu, 20 Nov 2025 09:09:10 GMT</pubDate>
      <description>Bytebase 3.12.1 adds stdout audit logging, AWS cross-account IAM auth, GitOps Service Agent role, and BigQuery dry-run SQL validation.
• 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 IAM authentication is supported for database connections
• `GitOps Service Agent` role added to Bytebase RBAC for automated CI/CD workflows
• BigQuery SQL Editor now supports dry-run execution to validate queries before running them
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.12.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.12.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.12.0</guid>
      <pubDate>Thu, 06 Nov 2025 10:05:17 GMT</pubDate>
      <description>Bytebase 3.12.0 adds PostgreSQL State-based GitOps workflow, IdP-initiated SSO, and direct SQL Editor export.
• Add support for IdP-initiated SSO 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.
Breaking changes:
• Remove identity provider 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.11.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.11.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.11.1</guid>
      <pubDate>Thu, 23 Oct 2025 07:11:41 GMT</pubDate>
      <description>Bytebase 3.11.1 adds Apache Doris system view support, inactive session timeout config, and multi-query result export
• `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.
Breaking changes:
• The `--check-plan` option is removed from the `bytebase-action rollout` command; scripts using this flag will fail.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.11.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.11.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.11.0</guid>
      <pubDate>Fri, 10 Oct 2025 08:49:16 GMT</pubDate>
      <description>Bytebase 3.11.0 introduces configurable rollout requirements, Terraform enum updates, AWS Elasticsearch cross-account support, and instance labels.
• 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
Breaking changes:
• 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 IAM policy with `maximum_result_rows` in `QueryDataPolicy`
• Standardizes CEL 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 == &quot;HIGH&quot;`
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.10.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.10.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.10.1</guid>
      <pubDate>Thu, 25 Sep 2025 07:54:13 GMT</pubDate>
      <description>Bytebase 3.10.1 adds project labels (64 key-value pairs), transaction mode toggle in Plan, and MySQL isolation level selection
• 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
• New API syntax for database label filter: `labels.region == &quot;asia&quot;`
• Display tasks in a flat list on the Data Export issue page instead of grouped by stages
Breaking changes:
• The standalone API field `DisableCopyDataPolicy` is removed; use `QueryDataPolicy` instead.
• Database label filter syntax changed from `label == &quot;region:asia&quot;` to `labels.region == &quot;asia&quot;`
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.10.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.10.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.10.0</guid>
      <pubDate>Thu, 11 Sep 2025 07:31:29 GMT</pubDate>
      <description>Bytebase 3.10 adds Cassandra data masking, a TLS verification toggle for instance setup, and GitHub Actions job summaries
• 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.
Breaking changes:
• 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`.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.9.2</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.9.2</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.9.2</guid>
      <pubDate>Thu, 28 Aug 2025 08:41:47 GMT</pubDate>
      <description>Bytebase 3.9.2 adds hard-delete for projects/instances, draft plan modification, Entra ID SCIM normalization, PostgreSQL CREATE RULE support, and API pagination/filtering.
• 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 &apos;one-click ready for review&apos; 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
• 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
Breaking changes:
• The `UpdateMask` values in the `UpdatePolicy` API now omit oneof type names, using field names only (see PR #17240)
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.9.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.9.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.9.1</guid>
      <pubDate>Thu, 14 Aug 2025 08:22:27 GMT</pubDate>
      <description>Bytebase 3.9.1 adds file-backed PG_URL hot-reload, AWS OpenSearch IAM auth, and Terraform sync_databases/masking exceptions
• 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
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.9.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.9.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.9.0</guid>
      <pubDate>Thu, 31 Jul 2025 09:29:08 GMT</pubDate>
      <description>Bytebase 3.9.0 introduces a new database CI/CD experience with multi-task rollback and plan draft staging.
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.8.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.8.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.8.1</guid>
      <pubDate>Thu, 17 Jul 2025 07:28:57 GMT</pubDate>
      <description>Bytebase 3.8.1 adds preview database CI/CD workflow, SQL Server spatial index support, and Redshift txn-mode directive.
• `-- 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
Breaking changes:
• `default_expression`, `default_string`, and `default_null` fields in `ColumnMetadata` are removed from the API; use the unified `default` field instead.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.8.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.8.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.8.0</guid>
      <pubDate>Thu, 03 Jul 2025 08:42:46 GMT</pubDate>
      <description>Bytebase 3.8.0 adds query result row limits and multi-domain configuration support
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.7.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.7.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.7.1</guid>
      <pubDate>Thu, 19 Jun 2025 07:41:16 GMT</pubDate>
      <description>Bytebase 3.7.1 adds `use_ssl` field for Terraform database connection SSL certificates and moves Review Center to `/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`
Breaking changes:
• Review Center routes have changed from `/review-center` to `/plans`, breaking any direct links or bookmarks to the old paths.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.7.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.7.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.7.0</guid>
      <pubDate>Thu, 05 Jun 2025 07:53:01 GMT</pubDate>
      <description>Bytebase 3.7 adds batch data export via issues, Trino data masking, and SQL Editor enhancements.
• `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` RPC 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
• 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
Breaking changes:
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.6.2</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.6.2</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.6.2</guid>
      <pubDate>Fri, 23 May 2025 05:36:22 GMT</pubDate>
      <description>Bytebase 3.6.2 adds database group queries, local query history, lazy execution to SQL Editor
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.6.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.6.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.6.1</guid>
      <pubDate>Thu, 08 May 2025 06:58:10 GMT</pubDate>
      <description>Bytebase 3.6.1 adds DML rollback for unique indexes and parallel rollout tasks
• `DML rollback` now supports `unique indexes` for MySQL, PostgreSQL, Oracle and MSSQL
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.6.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.6.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.6.0</guid>
      <pubDate>Thu, 24 Apr 2025 07:37:38 GMT</pubDate>
      <description>Bytebase 3.6.0 adds Trino/Cassandra support, OIDC group sync, PostgreSQL lock retry, and EXPLAIN for MSSQL/Redis read-only commands
• Adds basic support for the Trino database engine as a new datasource type
• Supports syncing OIDC IdP 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
• 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
Breaking changes:
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.5.2</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.5.2</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.5.2</guid>
      <pubDate>Thu, 10 Apr 2025 08:01:25 GMT</pubDate>
      <description>Bytebase 3.5.2 adds Cassandra SQL Editor support and pagination for list instances API
• `Support Cassandra in SQL Editor` enables querying and managing Cassandra databases directly within the Bytebase SQL Editor interface.
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.5.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.5.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.5.1</guid>
      <pubDate>Fri, 28 Mar 2025 02:27:20 GMT</pubDate>
      <description>Bytebase v3.5.1 adds Cosmos DB SQL syntax support and OpenSearch connectivity via Elasticsearch client.
• `SQL Editor` now supports `WHERE` clauses and `SELECT` projections for the **Cosmos DB SQL** syntax.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.5.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.5.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.5.0</guid>
      <pubDate>Thu, 13 Mar 2025 09:25:29 GMT</pubDate>
      <description>Bytebase 3.5.0 adds Azure IAM Auth for Cosmos DB &amp; SQL, paginated APIs, and DingTalk direct message webhooks
• 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
• 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 -&gt; General -&gt; Security -&gt; Maximum query time
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.4.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.4.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.4.1</guid>
      <pubDate>Thu, 27 Feb 2025 08:58:32 GMT</pubDate>
      <description>Bytebase 3.4.1 adds Terraform provider support for custom roles, instance licenses, and external secrets; enables new migration flags.
• 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
Breaking changes:
• 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase v3.4.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/v3.4.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/v3.4.0</guid>
      <pubDate>Thu, 13 Feb 2025 09:21:27 GMT</pubDate>
      <description>Index Advisor and SQL Sharing move to the free Community Plan; task check summary report gains Redshift support.
• `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
Breaking changes:
• The redundant `key` attribute of project has been removed.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.3.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.3.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.3.1</guid>
      <pubDate>Thu, 30 Jan 2025 06:24:36 GMT</pubDate>
      <description>Bytebase 3.3.1 adds 1-click DML rollback for Oracle, Vault AppRole auth, and partial-line execution in SQL Editor.
• 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
Breaking changes:
• The `concise` parameter has been removed from `GetChangelog` and `GetDatabaseSchema` APIs, so calls relying on this parameter will fail.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.3.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.3.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.3.0</guid>
      <pubDate>Thu, 16 Jan 2025 07:25:43 GMT</pubDate>
      <description>Bytebase 3.3.0 adds Release workflow, CosmosDB support, self-approval settings, and PostgreSQL 17/materialized view coverage.
• 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.
Breaking changes:
• Global masking takes precedence over column masking (previously, column masking took precedence).
• Masking levels are eliminated; semantic types map directly to masking algorithms.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.1.2</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.1.2</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.1.2</guid>
      <pubDate>Thu, 19 Dec 2024 07:22:28 GMT</pubDate>
      <description>Adds Lark IM/webhook integration, Redshift view definitions, and UI improvements
• Supports IM and webhook integration for Lark
• Display table and view definition for Redshift in SQL Editor
Breaking changes:
• The masking policy API `v1/{instance}/{database}/policies/masking` is removed; use `v1/{instance}/{database}/metadata` with the `columnConfigs` parameter instead.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.1.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.1.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.1.1</guid>
      <pubDate>Thu, 05 Dec 2024 07:37:14 GMT</pubDate>
      <description>Bytebase 3.1.1 adds customizable homepage, Redis Cluster node queries, and improved SQL Editor capabilities.
• Customizable homepage with a user-defined shortcut list
Breaking changes:
• Instance roles are removed from Database messages; use `GetInstance` or `ListInstanceRoles` to get instance role information.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.1.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.1.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.1.0</guid>
      <pubDate>Thu, 21 Nov 2024 06:55:40 GMT</pubDate>
      <description>Bytebase 3.1.0 adds PostgreSQL role selection, SQL Review Rules, SQL permission refactoring, and environment color customization.
• `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: &quot;Prohibit DDL on specific tables&quot; and &quot;Prohibit DML on specific tables&quot;.
• Ability to set custom colors for environments to improve visual distinction in the UI.
Breaking changes:
• 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
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.0.1</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.0.1</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.0.1</guid>
      <pubDate>Thu, 07 Nov 2024 06:54:45 GMT</pubDate>
      <description>Bytebase 3.0.1 adds environment policies for DDL/DML execution, BigQuery data masking, and SQL review upsert API
• 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`.
Breaking changes:
• 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`).
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
    <item>
      <title>bytebase 3.0.0</title>
      <link>https://github.com/bytebase/bytebase/releases/tag/3.0.0</link>
      <guid isPermaLink="true">https://github.com/bytebase/bytebase/releases/tag/3.0.0</guid>
      <pubDate>Thu, 24 Oct 2024 07:00:07 GMT</pubDate>
      <description>Bytebase 3.0 adds AI SQL generation, gh-ost support for MariaDB, and 1-click rollback for SQL Server DML.
• 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
Breaking changes:
• CEL parsed expressions no longer include unused `sourceInfo`, which impacts the structure of responses from `/v1/cel/batchDeparse`, `/v1/cel/batchParse`, and all IAM 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.
Full history on Cyber Toolchain: https://cybertoolchain.io/tools/bytebase</description>
    </item>
  </channel>
</rss>
