> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bytebase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bytebase 3.19.0 - Jun 04, 2026

> Just-in-Time Data Export

## 🔔 Notable Changes

* **Just-in-time data export** - Users can now request just-in-time data export access in the SQL editor and go through the approval workflow to export. Your existing data-export approval rules are migrated to the just-in-time approval flow. Please review and update the ordering of migrated rules according to the instruction on top of the Custom Approval page. See [Details](/security/database-permission/just-in-time#just-in-time-data-export).

* **Terraform** - Just-in-time data export flows through `REQUEST_ACCESS` approval, please add data-export rules (`request.data_export == true`) under the `REQUEST_ACCESS` source in your Terraform configuration - otherwise the next `terraform apply` will drop the auto-backfilled rules and JIT exports skip approval.

* **Active VCS user tracking for GitOps** — Non-bot PR/MR authors seen by `bytebase-release` workflows on GitHub, GitLab, and Bitbucket now count as active VCS users over a 90-day window and are enforced against the license user limit. Track usage and download the user list as CSV from the Subscription page.

* **bytebase-action enforces the version compatibility window** — `bytebase-action check` and `bytebase-action rollout` now fail with an error (previously a warning) when the action version is too far from the server version. Pin your CI to a compatible action version, or use the `cloud` tag on Bytebase Cloud. See [Change Details](#bytebase-action-compatibility-window).

## 🎄 Enhancements

* **MySQL** — Improve gh-ost prerequisite validation messages by distinguishing inaccessible binlog status, disabled binary logging, missing replication privileges, unsupported binlog format, and validation query failures.

* **SQL Editor** — Saving an untitled worksheet now prompts for a title, and searching the result panel indicates when nothing matches.

## 🐞 Bug Fixes

* **SQL Editor** — Fixed query execution and admin mode being blocked when opening the editor from a database page, along with several smaller UI fixes. Local editor state is now scoped per workspace on Bytebase Cloud.

* Restore the custom expiration time option when granting project roles, honoring the workspace maximum role expiration cap.

* Fix AI assistant compatibility with GPT-5-style models by omitting unsupported request parameters.

* Fix hosted MCP clients (claude.ai web, ChatGPT, VS Code for the Web) being rejected during OAuth dynamic client registration on self-hosted instances. Callbacks are pinned to exact vendor hosts, so arbitrary `https://` redirects remain blocked.

* **Self-hosted (Helm)** — Chart 1.1.3 restores `bytebase.version` as the single image knob; non-Azure deployments no longer silently resolve to the `latest` image.

* **Spanner** — Fix SQL Editor queries failing with "disallowed query type" in normal mode.

* **Doris/StarRocks** — Fix window functions inside a CTE body failing to parse in the SQL Editor.

* **TiDB** — Fix prior-backup rollback for alias-target multi-table DELETE, cyclic view references crashing query analysis, and advisor line numbers for statements separated by blank lines.

## 📃 Change Details

### bytebase-action Compatibility Window

`bytebase-action check` and `bytebase-action rollout` now **fail with an error** when the action/CLI version falls outside the supported compatibility window of the target Bytebase server (previously a warning).

| Deployment     | Compatibility requirement                                                                                   |
| -------------- | ----------------------------------------------------------------------------------------------------------- |
| Bytebase Cloud | Dated action versions (`cloud-YYYYMMDD`) within the last 7 days; use the `cloud` action tag to stay current |
| Self-hosted    | Same major version, within a 2-minor-version window of the server                                           |

| Version relationship      | Behavior                                 |
| ------------------------- | ---------------------------------------- |
| Exact match               | Success log                              |
| Within window, mismatched | Warn and continue (unchanged)            |
| Outside window            | **Error — command exits non-zero (new)** |

**Action required:** pin your CI to an action version within the window of your server version (self-hosted), or use the `cloud` tag (Cloud).

## ⚙️ Install and Upgrade

* [Fresh install](/get-started/self-host/deploy-with-docker)

* [Upgrade](/get-started/self-host/upgrade)

*Before upgrading: 1) Back up the [metadata](https://www.bytebase.com/docs/administration/back-up-restore-metadata/) — in-place downgrade is not supported. 2) Do not run multiple containers on the same data directory. 3) Terraform users: upgrade Bytebase server first, then apply the new Terraform config.*