Bytebase
Database CI/CD and schema change management platform
Bytebase 3.24.1 fixes connection leaks and brings MCP and AI settings into Terraform.
◆Recent moves
- 8d ago
Bytebase 3.24.1: connection leak fixes, MCP settings in Terraform
3.24.1 fixes memory growth with Cloud SQL IAM auth and connections left open in tenant mode, and Terraform provider 3.24.0 can now manage the MCP capability and AI provider settings. It lets teams set the agent access policy from 3.23 as code.
View source ↗ - 22d ago
Bytebase 3.24: MCP agents can request and approve access
⚡ SPARK3.24 builds on the 3.23 MCP access policy: in Read-write mode an agent can request just-in-time access, approve or reject issues, and manage masking exemptions, with the user confirming in their MCP client. It moves Bytebase's agent support from reading data to operating the approval workflow itself.
View source ↗ - 1mo ago
SQL Editor direct DDL/DML execution becomes an explicit opt-in
3.23.1 turns the ambiguous Environments field on DDL/DML roles into an explicit Direct DDL/DML execution switch, off by default, after owners routinely granted approval-free execution everywhere by accident. It applies the safe-default logic of the MCP policy to human roles, alongside clearer task run logs and plan review comments.
View source ↗ - 1mo ago
MCP access policy: disable, read-only or read-write per workspace
Adds a workspace-level MCP access policy (Disabled, Read-only, Read-write), with new workspaces defaulting to Read-only. It extends the governance arc from human approvals to AI-client sessions.
View source ↗ - 2mo ago
GPT-5 support and searchable service accounts in grant picker
GPT-5 support for AI features and searchable service accounts in the grant picker. Maintenance-grade, but it keeps the AI assistant current while the access-grant flow gets smoother.
View source ↗ - 2mo ago
Worksheets become Saved Queries with per-object sharing
Worksheets become Saved Queries with per-user and per-group Viewer/Editor sharing, folders and favorites. The SQL Editor gains the same object-level permission model the rest of the product is moving toward.
View source ↗