Bytebase Files

🎄 Enhancements

• Plan detail page improvements.

• Refreshed layout. Cleaner layout with at-a-glance plan-check status across all specs and consistent database-target display through every phase.

• Release-backed plan flow simplified. Release-backed (GitOps) plans now show only two phases — CHANGES and DEPLOY — with minor UI refinements throughout.

• SaaS: MCP discovery works against Bytebase Cloud. MCP clients (Claude Code, Cursor, etc.) can now complete the OAuth flow against cloud.bytebase.com without manual configuration.

• PostgreSQL — Compatible with pgbouncer transaction pooling (statement cache disabled) and PostgreSQL 18 (built-ins like uuidv7() and 80+ others are recognized by SQL analysis and schema diff).

• TiDB — DML rollback / prior-backup preview now works. Queries against columns added out-of-band trigger the standard metadata-resync-and-retry path (matching MySQL / PostgreSQL).

• gh-ost migrations honor the configured data-source SSH tunnel for both the MySQL connection and the binlog reader.

• Query data source — Non-read-only automatic SQL Editor queries now use the admin data source when the query data policy allows it. Read-only queries are unaffected.

• Demo mode removed. The --demo server flag has been removed. This mode was for internal demos (it loads a baked-in SQL dump and a sample admin) and was never intended for production use — if you have --demo in your startup script, drop it and configure instances and users normally.

🐞 Bug Fixes

• Workload identities are distinguished from service accounts in the members table, and the graphical CEL expression editor is restored for project member role grants.

• Large target sets in the issue / plan target overflow view no longer freeze or mis-render.

• The plan list creator filter actually returns users now, and the review badge ("Bypassed" / "Under Review") reads consistently with plan detail.

• PostgreSQL — Multi-host failover honors Bytebase's configured TLS material on every host, not just the primary.

• The Sync Database success toast renders the actual database name instead of the literal {{name}} placeholder.

🏗️ Terraform Update

• Terraform provider 3.18.1 required — Marks the webhook URL as write-only and adds APP_IM support to bytebase_setting. See Migration Guide.

https://github.com/bytebase/bytebase/compare/3.18.0...3.18.1

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