Bytebase Changelog

🚀 New Features

• Configure policy via the Terraform Bytebase Provider.

🚀 New Features

• Added support for MongoDB. 🍃
• View ER Diagrams with the new Schema Diagram.
• Support editing PostgreSQL schema via the UI-based Schema Editor. 🐘

🚀 New Features

• Workspace admin and DBA can now view audit logs.
• Support CRUD database role (only for PostgreSQL) via Terraform Provider. Read the docs.
• 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).
• Support online migration for UI workflow under tenant mode.

🚀 New Features

• Support data access control.
• Schema Editor for MySQL.
• Check "Mark as done" to skip a task.
• The issue creator can mark an issue as "Needs attention", which is highlighted in the assignee's view.

🚀 New Features

• Support managing environment and instance via Terraform provider: https://bytebase.com/docs/get-started/terraform
• Support synchronizing schema for PostgreSQL🐘 Currently in beta, we support Schema, Table, Index, Constraint, and Sequence so far.
• Support masking column-level sensitive data for MySQL🐬.
• New UI for Admin mode of SQL Editor.

🚀 New Features

• Support syncing schema for MySQL.
• Support approving issues via Lark (Feishu).
• Support SQL Review CI in the GitOps workflow.
• DBAs and workspace admins can run SQL statements in Admin mode from the SQL Editor.
• Support altering multiple databases on tenant mode.

🚀 Features

• Added 31 review rules for MySQL.
• Support DDL validation in SQL review.
• Support canceling gh-ost sync tasks.

🚀 Features

• Support read-only data source for read-replica instance.

🚀 New Features

• Added "LGTM" inspection for issues, allowing multiple members to review the same issue.

🚀 New Features

• AWS S3 is now supported as a backup storage backend.
• Added a new onboarding guide.

🚀 New Features

• Integrate PostgreSQL Explain Visualizer 👀.
• Support in-place backup restore for PostgreSQL.
• Support PITR to a new database for MySQL.
• Users can mark an environment as "protected", and a shield badge 🛡️ will show up next to its name.
• Users can view, copy and export server-side error info on Settings > Workspace > Debug Log.

🚀 New Features

• SQL Review is now available on the GitHub Action Marketplace! 🐱

🚀 New Features

• Support SQL review for PostgreSQL with 13 rules: SQL Review

• Support using GitHub.com both as the VCS integration to manage database schemas and as the authentication provider to allow users to use their GitHub.com accounts to log in to Bytebase.

• Restore a database to the time point before the last migration with one click.

🚀 New Features

• 👻 Added support for gh-ost, online schema migration for large MySQL tables (Beta).

• Updated the way help tips are displayed, using a side drawer instead of the pop-up tips.

• Added length limit for table, column, index, foreign key, unique key names.

• Added a new rule to disallow foreign keys on a table.

• Added a new rule for naming convention when dropping a table.

🚀 New Features

• In-place Point-in-time Recovery for the database (preview version).

• Added GET /v1/sql/advise OpenAPI.

It allows users to perform SQL reviews via API after configuring the schema review policy. Users can access its API documentation via /swagger/index.html once they start their Bytebase service.

🚀 New Feature

Schema Review for SQL Editor

• After setting up the schema review policy, if the SQL statement violates the error rule, Bytebase prevents SQL execution and shows error messages
  • Users can change the rule level from "Error" to "Warning"
    • If the SQL statement violates the updated schema review policy, Bytebase will run the SQL, but the warning message will display "Warning"
    • If schema review passes, Bytebase will run the SQL normally

• Enable schema review policy configuration in environment
• Users can configure a schema review policy for a particular environment. The schema review policy can be configured through both schema review policy dashboard and environment dashboard
• Both rule level and rule configuration can be changed
• After creating a schema review policy, users can view, edit or delete the policy any time they like
• Display schema review results in the issue detail page if the schema review policy is configured

🎄 Enhancement

• Add archive checkers for environment/project/instance
  • Ensure the environment has no instance before it's archived
  • Ensure the project has no database before it's archived
  • Ensure all databases in the instance are under the default project before the instance is archived
• UI improvements for tenant-mode deployment
• Improved PostgreSQL schema dump.
• The owner of newly created PostgreSQL schemas will be the same as the database owner by default.
• Display applicable conditions for Environment policies.

• Update CLI docs

bb CLI is the command-line tool of Bytebase, helping developers integrate MySQL and PostgreSQL schema change into the existing CI/CD workflow. By integrating bb with your existing CI/CD system (GitLab CI, GitHub Actions, etc.), you can bring all best practices of CI/CD to the database.

🚀 Features

• From SQL Editor, you can now sync your SQL scripts stored in the linked VCS system.

• Star the sheets to save them in a list.

• List database extensions for PostgreSQL.

• Support creating a Postgres database with an owner.

• Launch the Chinese version of our official website.

🎄 Enhancement

• Add custom project webhook.

  The webhooks we currently support are pre-defined and basically can only do notifications, custom webhook can be more flexible to interact with some external systems (for example, external systems want to sense the status of an issue and do some different operations based on the issue status).

• Add "Format on save" checkbox on the issue detail page.

  With the default check, when the users click the "Create issue" button, the SQL statement will be automatically formatted.

• Add "Sync schema afterward" checkbox on the instance create and detail page to allow users to disable the database sync if needed.

  Currently, we sync the schema upon adding/patching the instance. This provides a better UX since the user will see the schema after adding the instance. However, for instances having large schemas, the request will timeout and prevents them from adding the instance at all. The added checkbox only appears if connection-related info is changed.