• 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.

🐞 Bug Fix

• Fix bugs that prevent GitLab providers from being added or modified under certain circumstances, and improve the overall experience of integrating GitLab for users.

🎠 Community

• Open source the design doc for Point-in-Time Recovery (PITR) https://github.com/bytebase/bytebase/blob/main/docs/design/pitr-mysql.md.
  In order to enhance Bytebase's backup recovery capabilities and allow users to restore the database state to any point in time, we designed the Point-in-Time Recovery (PITR) feature integrated into the Bytebase workflow.

• Thanks to @unknwon for the PR feat: implement add GitHub as Git provider.
• Thanks to @Cluas for the PR feat: add custom project webhook.
• Thanks to @tnir for the PRs chore: update GitLab logos updated in 2022 , docs: fix typos in types/pipeline/README.md, fix(ui): tweak warning message in readonly mode.

📕 Installation and Upgrade

Follow https://github.com/bytebase/bytebase#installation. If you upgrade from a previous version, just restart after obtaining the new release binary.

Support storing Bytebase metadata in the external PostgreSQL

Use the --pg option to specify the database endpoint upon launching Bytebase.

🚀  Features

bb CLI Support --dsn option in CLI

Support data source name (DSN) formats to connect databases in CLI, e.g. --dsn mysql://user:passwd@host:port/dbname?opt1=val1&opt2=val2

Add installation script of bb CLI

User can install bb CLI with only one command /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/bytebase/bytebase/HEAD/scripts/install_bb.sh)" . Previously, users needed to go through several steps from downloading on GitHub Release, decompressing and manually moving the files to executable file directory.

Add dashboard page to manage all SQL sheets

Introducing the SQL sheet dashboard page as users can view all related sheets in a table view.

Admin page to view all projects

Users whose roles are Owner and DBA in Workspace can view all projects under Settings.

Added /healthz health check endpoint

This enables serverless platforms like render.com to point its health check endpoint to /healthy.

🎄 Enhancement

Expose Visit Default Project button explicitly

The Default Project is the special project holding the databases synced from the database instance. Users usually need to visit this project to transfer the database to their own projects.

🎠  Community

• Thanks to @cluas for the PR docs: update schema-update-guide link #1104, PR style: error no capitalized && switch && De Morgan's laws #1125, PR fix: should use request context #1131, Pr fix: handle gitlab error case #1132, PR fix: wrong type cause role_provider missing #1136、
• Thanks to @sagungargs15 for the Issue Docker on AWS Fargate | database "bytebase" does not exist | database "bb" does not exist #1135
• Thanks to @Austin Ziegler for Issue No linux/arm64 docker image #1119

📕 Installation and Upgrade

Follow https://github.com/bytebase/bytebase#installation. If you upgrade from a previous version, just restart after obtaining the new release binary.

Release MySQL Database Review Guide

Database Review Guide lists all the rules in schema change review, from the naming convention of Table, Column, and Index to the designated WHERE clause. We provide rule templates for the MySQL Dev and Prod environments. DBAs can configure the rules manually based on our templates, and generate images for internal reference.  Meanwhile, we are actively working on the following area:

• Add more rules. We also welcome DBAs' suggestions at Issues · bytebase/bytebase
• Integrate those rules into the Bytebase product by detecting rule violations automatically.

Currently, we only support MySQL. We will add PostgreSQL support later.

🚀 Features

• Toggle Debug mode at runtime for easier troubleshooting

Only OWNER and DBA can toggle Debug mode

When the Debug mode is enabled, you can see the internal error messages on the web console, and more details are included in the logs. Previously, users can use --debug on Bytebase startup to do this. Now you can toggle this setting at runtime. Debug mode is a global setting and will affect all users, thus only OWNER and DBA can toggle it. It's expected to be temporarily turned on for troubleshooting issues.

🎄 Enhancements

• [SQL editor] support more types of EXPLAIN queries on the basis of EXPLAIN SELECT, such as EXPLAIN INSERT.

🎠 Community

• Precompile various executable file formats in the released version: Bytebase server and CLI binary will be released on the [GitHub release page]. Currently, Bytebase supports Linux, Darwin, x86_64, arm64.
• Thanks to @unknwon for the PR feat: allow exchange OAuth token without an existing VCS #1007
• Thanks to @tison for the PR feat: support to specify external pg instance as metadata storage #1030
• Thanks to @milkwine for the PR fix: backup failed when dash('-') in database name #874
• Thanks to @Cluas for the PR fix: tenant mode VSC with DatebaseNameTemplate task execute error #1071
• Thanks to @0xflotus for the PR PR chore: fix small typo error #805

📕 Installation and Upgrade

Follow https://github.com/bytebase/bytebase#installation. If you upgrade from a previous version, just restart after obtaining the new release binary.

​💡 Our official documentation switches from gitbook to bytebase.com/docs. All the documents are now in our Github repository. This will help improve our coordination efficiency in documentation greatly. Now developers can follow https://bytebase.com/docs/document-write-guide to commit your changes.

🚀 Features

• Support branding customization (available in Team/Enterprise Plan)

🎄 Enhancements

• [SQL Editor] Highlight the editing SQL query block

• [SQL Editor] Add SQL query format button

• Bump tailwind css to v3. JIT mode is also enabled to support arbitrary values.
• Switch frontend package manager from yarn to pnpm, helping developers to save time and disk spaces.

🎠 Community

• Open source an Employee sample database for MySQL https://github.com/bytebase/employee-sample-database-mysql  based on https://github.com/datacharmer/test_db. The sample database will apply to daily tests, data presentation and document tutorials. We prepare 2 datasets:

- Full dataset (~170 MB) including 300024 employee records.
- Small dataset (~6 MB) including 10000 employee records.

• We're working to support online schema change for MySQL using gh-ost. You can check the design doc at https://github.com/bytebase/bytebase/blob/main/docs/design/gh-ost-integration.md and give feedback if you are a DBA or a gh-ost user.
  
• Switch license from APL 2.0 to MIT.
  
• Thanks to @unknwon for the PR feat: add migration for GITHUB_COM to be a valid Git and role provider #941
  
• Thanks to @Sepush for the PR refactor: use script setup&fix type #856

📕 Upgrade instruction

For a fresh installation, follow https://github.com/bytebase/bytebase#installation.

What's Changed

🚀 Features

• Support instance read-only connection. Once configured, Bytebase will use this user to query databases in SQL Editor and will use it in all read-only scenarios in the future.

🎄 Enhancements

Tenant Mode

• Enable Data Change (DML) for tenant mode projects.

SQL Schema Review

• Allow users to edit SQL statements.
• Allows retry for failed migration with invalid SQL statement.

SQL Editor

• Change the save sheet logic. Save the sheet when clicking the save button or using the shortcut (CMD + S).

Installation Improvement

• Improved installation on Linux platform.

🐞 Notable bug fixes

• Several security enhancements.

🎠 Community

• Thanks to @0xflotus for PR chore: fix small typo error.
• Thanks to @milkwine for PR fix: backup failed when dash('-') in database name.

📕 Upgrade instruction

For a fresh installation, follow https://github.com/bytebase/bytebase#installation.

🚀 Announce our Team Plan

With over a year of hard work and 3500+ commits, we finally reach the milestone to announce our 1.0.0 version and our Team Plan. The Team Plan includes:

• Role-Based-Access-Control (RBAC) with Owner, DBA, Developer roles catering to the collaboration during database development.
• Login using GitLab account.
• Sync project membership from the linked GitLab project.
• SQL backward compatibility check and schema drift detection.
• Per-environment schema review and backup policy.

The price starts at $29 per instance per month. Please visit our pricing page for more details.

You can visit https://hub.bytebase.com/pricing to purchase a subscription license and manage your team plan subscription in Settings page.

🎄 Enhancement

SQL Editor

• Add an EXPLAIN button adjacent to the run button.

• Redesign the database connection navigation and connection status.

• Run non-SELECT SQL navigate to the different workflow.

Sync project members from GitLab

If a project is linked with GitLab repository, one can sync that repository's membership to the project's membership.

Improved tenant project pipeline UI

We improve the layout for showing the current database schema change progress across all tenants.

Misc

• Switch to use PostgreSQL for storing Bytebase metadata. This enables us to handle more complex scenarios down the road.
• Add quickstart for preparing an environment including Bytebase, GitLab (macOS Apple Silicon) and ClickHouse Cluster.

🐞 Bug fix

SQL Editor

• Query result table cover display.

• Query result table attributes order

🌄 Sunset

Retire issue rollback feature
Previously, Bytebase allows user to specify a rollback SQL for the rollback. And if user chooses to rollback the SQL, Bytebase will use the rollback SQL to create that rollback SQL. This only sounds good in theory, because in reality, it's already a big hurdle to write a good schema change SQL, it would be even challenging to ask the developer to provide a correct rollback SQL at the same time.

Thus, we decide to retire this feature. Meanwhile we already have ideas for a much better solution without requiring developer to write the rollback SQL manually. Please stay tuned.

🎠 Community

• Thanks to @Innei for PR fix(bbmodal): subtitle bg keep out modal container content & add max-height padding.
• Thanks to @tisonkun for PR refactor: update tidb dependency and remove workaround replacement

📕 Upgrade instruction

For fresh installation, follow https://github.com/bytebase/bytebase#installation.

If you upgrade from the previous version, there is some breaking schema change. Please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 New Features

• SQL editor supports sheet sharing.

🎄 Enhancement

• Searchable member selector.

• Database labels can be managed as normal properties. Database label related features are available for standard mode projects now.

• Show comprehensive schema comparison when schema drift is detected.

• Add quickstart for MySQL and Clickhouse.  You can choose to have MySQL or Clickhouse run automatically with Bytebase without additional installation. Thanks @showsmall  for the suggestion.

🐞 Bug fix

• Prevent XSS in SQL editor.
• Filter improper authorization of user inbox.

🎠 Community

• Our gratitude goes to @boyapatisandeep for the detailed bug report and @NickStepanov for the baseline issue
  
• Thanks to @Juneezee https://github.com/bytebase/bytebase/pull/264 @wuhan005 https://github.com/bytebase/bytebase/pull/340 @cosmtrek https://github.com/bytebase/bytebase/pull/410 @stormcat24 https://github.com/bytebase/bytebase/pull/453 for all your contribution!

📕 Upgrade instruction

For fresh installation, follow https://github.com/bytebase/bytebase#installation.

If you upgrade from the previous version, there is some breaking schema change. Please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 New Features

Multi-tenancy Database Management

Say you have many databases that use identical database schemas and need uniform management. For example, my highly-available service stores database data in different locations or data centers; or my SaaS service stores every customer/tenant's database data in their own databases. This multi-tenancy database management feature allows you to manage and update schemas for these hundreds of databases consistently and conveniently.

• Intelligent database management for tenants using identical schemas.
• Creating and managing database labels used for searching resources and identifying tenants.
• Flexible tenant database deployment such as multi-stage regional deployments.
• Schema updates are applied to all tenants consistently. Adding a new tenant database will use the same schema from existing tenants.

SQL Editor

• Support keeping multiple editors under different tabs.

• Seamless transition to the schema change (DDL) / data change (DML) workflow from the SQL Editor.

• Project based permission control.
• Save Query: support saving the SQL statement, search it with highlight and delete.

• Query History: record all the executed queries.

Signup and login via GitLab EE/CE

Most in-house dev teams use GitLab EE/CE to host their code. Bytebase has already supported VCS integration with GitLab to manage database schemas. We now further enhance the integration to allow users to use their GitLab EE/CE account to login Bytebase. Thanks @siu91 for the suggestion https://github.com/bytebase/bytebase/issues/27.

Support data change (DML) workflow

Besides the schema change (DDL) workflow, we now also support the DML workflow. Thanks @TBACEJ for the suggestion https://github.com/bytebase/bytebase/issues/337

🎄 Enhancement

• Surface detailed error to the UI when --debug is enabled when starting Bytebase

🐞 Bug fix

• Fix the VCS schema write back after migration when the git branch name contains slash (e.g. features/foo) https://github.com/bytebase/bytebase/issues/396
• Fix the MySQL 8.0 window functions syntax error https://github.com/bytebase/bytebase/issues/175

🎠 Community

• We are on the list of “The fastest-growing open-source startups in Q4 2021” by Runa Capital  https://runacap.com/ross-index/q4-2021/

📕 Upgrade instruction

For fresh installation, follow https://github.com/bytebase/bytebase#installation.

If you upgrade from the previous version, there is some breaking schema change. Please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 New Features

(Preview) SQL Editor

• Auto-complete and context menu.
• Run SQL statement (only allow SELECT query) and display the result in a table view.
• Navigate among different database connections via the left tree panel.
• Display table schema info on the bottom left side panel.

🎄 Enhancement

kbar quickstart

User can now use cmd+k to invoke the command bar to quickly navigate among different Bytebase sections.

Refactor the underlying VCS module to make it plugable.

This ease the path to support other VCS systems like GitHub, BitBucket.

🐞 Bug fix

• Fix the issue when we are unable to write back the latest schema to the Git repository after the migration succeeds.

🎠 Community

Preview environment for each PR

Now every PR will create a unique preview environment. This makes it easy to collaborate among author and reviewers.

• Bytebase Sticker Collection V1.0 is ready  https://bytebase.com/brand

• Thanks to @Juneezee 's PR refactor: move from io/ioutil to io and os packages

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from previous version, there is some breaking schema change. Please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 New Features

你好, 中文 Chinese Language Support

Bytebase now officially supports simplified Chinese. User can toggle the language from the top-right profile dropdown.

Earliest allowed time for executing a task

Now, user can specify the earliest allowed time for a task to be executed by Bytebase. If specified, task will not be executed until that specified time.

🎄 Enhancement

Logging activity for altering SQL statement

We will log any change to the SQL statement now, and send an inbox message to the relevant people.

Modal showing detailed check status

When the assignee opens the modal to approve an issue, she can now view the detailed check status by opening a stacked modal.

🐞 Bug Fixes

Postmortem: Postgres CREATE DATABASE cannot run inside a transaction block

Story: In a change to support ClickHouse, we were unifying SQL statement execution to a shared function. Bytebase supports many databases including MySQL, Postgres, Snowflake, TiDB, Clickhouse - Yes, more to come. We are trying to use the same interface for interacting with all database types if possible. Since ClickHouse cannot execute multiple statements in a single db.ExecContext(), we split the multi-statement string into multiple single-statement strings and use a transaction to execute the migration statements. In fact, we should execute migration transactionally so that previous executions will be rolled back upon failures, otherwise migration will leave the database in an inconsistent state. However, this change caused Postgres CREATE DATABASE to fail because Postgres CREATE DATABASE statement cannot be used inside a transaction (see reference 2). In the fix, we would skip using transactions for Postgres CREATE DATABASE statements.

Lessons learned: different databases are different, and users learn lessons usually in a hard way unfortunately. This is exactly why users should use Bytebase to manage database schemas, because our software can save you from hitting these blocks. We will also put effort into integration tests to cover critical user journeys for various database types so that we can catch these errors early on. Even though Bytebase is still in Alpha, we would like to share these stories transparently to readers who are interested in databases.

Reference: https://www.postgresql.org/docs/current/sql-createdatabase.html
Notes section: CREATE DATABASE cannot be executed inside a transaction block.

Fix for auto-increment starting value in MySQL schema

MySQL allows AUTO_INCREMENT to start with a value other than 1. However, this starting value in table schema (MySQL’s SHOW CREATE TABLE native schema export) would change when rows are inserted. For example, AUTO_INCREMENT=20 will be AUTO_INCREMENT=22 when the table gets two more rows. This would cause Bytebase’s schema drift detection to complain when AUTO_INCREMENT tables are mutated. Starting with this release, we will exclude this starting value in a schema-only dump.

By looking at typical MySQL user journeys, starting value in the schema only makes sense for a database dump with both schema and data since the restore of this dump will make the new database an exact copy of the previous database. This starting value is meaningless in a schema-only dump for most use cases, otherwise, users should be setting the starting value explicitly themselves after the restore.

Auto refresh GitLab access token on expiration

Access token expiration was added to GitLab 14.3 release and became the default. This default wasn’t compatible with Bytebase’s GitLab Version-Control-System (VCS) version control integration because tokens passing the 2-hour expiration window became invalid. This Bytebase release supports GitLab 14.3 by refreshing tokens upon expiration, providing enhanced security to the community and beyond.

🎠 Community

• Add i18n guide docs to help community member start contributing.
• Our gratitude goes to @linucksrox especially for his detailed bug report  and @suzaku again for the continuous contribution.

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from previous version, there is some breaking schema change. Please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 New Features

cmd+k command bar experience

User can now use cmd+k to invoke the command bar to quickly navigate among different Bytebase sections.

Add database backup webhook

User can set up a webhook endpoint for the database and after a successful backup, Bytebase will send a POST request to the configured webhook endpoint.

As an example, user can use this feature to integrate with Better Uptime's Heartbeats feature to monitor the status of database backups. In case Bytebase does not regularly send requests to Heartbeat endpoint configured on Better Uptime, Better Uptime will trigger the corresponding alert rule.

Gitpod Code Preview

We added one-click button on our GitHub front page to launch Bytebase in Gitpod. Now user is only one click away from having a fully-fledged dev environment to play with Bytebase!

🐞 Bug Fixes

• Fix tooltip position
• Add the missing EVENT privilege to the instruction for configuring the MySQL user connection

🎠 Community

• Add commit guide docs
• Special shout out to @suzaku for contributing PRs (a lot!)

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from previous version, there is some breaking schema change. Please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 Branding update

• Updated logo font to use the open sourced Cal Sans Semibold.

🎄 Enhancement

• New illustration for signin/signup page, 403, 404 pages.
• New wizard on home page.
• Properly populate instance default host in create instance form.

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from 0.8.x, no migration needed. If you upgrade before 0.8.x, there is some breaking schema change, please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 New Features

Support Snowflake ❄️

Snowflake® is a cloud-based data storage and analytics service. It allows corporate users to store and analyze data using cloud-based hardware and software.

🐞 Notable Bug Fixes

• Mark the migration history as failed if the migration did fail.
• Fix the PostgreSQL schema sync from AWS RDS and Google Cloud SQL #30.
• Allow Bytebase to run on non-https host #31.

🎄 Enhancement

• Improve migration history table layout and surface migration SQL from the list.

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• This version has some breaking schema change, please contact support@bytebase.com and we will help you manually upgrade to the new version.

🚀 New Features

Support ClickHouse 🖱🏠

ClickHouse® is an open-source, high performance columnar OLAP database management system for real-time analytics using SQL and it has a similar schema management requirement see #issue14.

🎄 Enhancement

• Refresh the database list immediately after updating the instance connection info.
• Add shortcut button to create new database from the instance detail page.
• Hide empty password checkbox in instance creation form. User can already leave the password field empty, so there is no need to have an extra checkbox.

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from 0.7.x, no migration needed. If you upgrade before 0.7.x, there is some breaking schema change, please contact support@bytebase.com and we will help you manually upgrade to the new version.

This is a security fix release. Please consider upgrading it.

🎄 Enhancement

• Fixed a bunch of security issues found by huntr.dev

1. Reject the current user operation if the user has just been de-activated.

2. Secure the access token to prevent CSRF attack.

3. Disallow Bytebase to be loaded in an iframe.

🎠 Community

• Thanks @jiweiyuan to fix our first good first issue

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from 0.7.0, no migration needed. If you upgrade before 0.7.0, there is some breaking schema change, please contact support@bytebase.com and we will help you manually upgrade to the new version.

This release takes a bit longer because we are packaging couple exciting features in it. Let's check them out.

🚀 New Features

Support PostgreSQL 🐘 🐘 🐘

Our team really love PostgreSQL and we are the ones delivering the initial launch of managed PostgreSQL at Google Cloud SQL. So we are really happy to announce the official PostgreSQL support in Bytebase. Elephant in the room ✅

Schema drift detection

Bytebase will periodically compare the recorded schema with the actual schema and expose the drift if occurs. We also provide a side-by-side view to show the diff.

Introduce Anomaly Center

Many things can go wrong for your database and unnoticed until an outage happens. We are always thinking of a proactive way to help user catch those problems. Today we introduce Anomaly Center, our attempt to address this challenge. A background process will periodically scan potentially anomalies on the managed instances and databases, then expose them in a holistic view.

We currently detect following anomalies and will add more in the future:

• Database connection issue
• Backup policy violation
• Expected backup missing
• Schema drift
• Migration schema missing

Backward compatible schema migration check (MySQL/TiDB)

In the last release, we introduce the task check system and introduced the basic SQL syntax check. In this release, we advance the check to catch backward incompatible schema migration (e.g. RENAME TABLE). Introducing backward incompatible schema changes is one of the most common mistakes made by developers and enforcing backward compatible schema change is the standard practice adopted by many engineering organizations. Bytebase now automatically checks all common incompatible schema change scenarios and surface them in the SQL review panel:

Backup schedule enforcement

Owner and DBA can now enforce backup schedule policy for the specific environment. e.g. require daily backup for production environment.

🎄 Enhancement

• Improve the onboarding workflow to establish the initial schema baseline.
• Allow user to specify empty password when connecting the instance (though not recommended).
• Sync detailed "View" schema info.
• Many other UX improvements and we plan to write a separate article to talk about those small but also meaningful improvements.

🎠 Community

• We revamped our landing page with the wonderful illustration. The figure derives from our logo and we plan to continue this path to strength our branding identity.

• We have open sourced our take-home interview assignment.  And yes, we are looking for talented frontend engineer and full-stack engineer to join our remote team. Checkout job details.

📕 Upgrade instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from previous version, then it requires manual schema change, please contact support@bytebase.com and we will assist you to perform the manual upgrade.

Update instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from previous version, then it requires manual schema change, please contact support@bytebase.com and we will assist you to perform the manual upgrade.

🚀 New Features

Support TiDB

TiDB is an open-source, cloud-native, distributed SQL database for elastic scale and real-time analytics.

Add task check to gate schema change

• This works similar as GitHub merge request check. The schema change only proceeds if all check pass.
• In this initial launch, we enforce 2 checks, db connection check and syntax check for the schema change task. We plan to add more checks like advanced SQL analyzer in the future.

🎄 Enhancement

• Show VCS push event info in the migration history detail page.
• Improve UX for configuring the instance connection.
• Improve UX for transferring database between projects.
• Create dedicated migration history tab for a particular database.
• Add baseline migration history record upon creating the database.

🎠 Community

• A special thanks to TiDB's open source compatible MySQL parser. It saves us a lot of effort to implement our syntax checker.
• We have migrated changelog to our newsletter system as well. So in the future, new changelog will also be delivered to your email automatically.

🚀 New Features

Project level activities

• Database ownership transfer
• Membership change
• Version Control Workflow based push event

Version Control Workflow enhancement

• Allow user to specify the migration file path template. Detailed guide
• Allow user to specify the schema path template. This is useful to let repository always keep a complete schema of the corresponding database. Detailed guide
• Record schema snapshot in every migration history record

A dedicated page for individual migration history

The page shows applied migration statement as well as the schema snapshot after the migration.

🐞 Important Bug Fixes

MySQL 5.7 compatibility

In the previous version, Bytebase couldn't sync the migration history properly because it used a MySQL 8.0 only feature.

🎄 Enhancement

• Make task scheduler run task asynchronously.
• For database creation task, add database and its creation state (pending or created) to the issue sidebar.
• For database schema update task, show indication if it's a baseline migration.
• Add schema version link to the backup table row.

🎠 Community

• Thanks @chenliang for providing a detailed bug report for MySQL compatibility issue and even suggesting the fix.
• Thanks @yaohui-wyh for the contribution.

Update instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from 0.4.0, you dont't need to do anything. If you upgrade from veresion before 0.4.0, then it requires manual schema change, please contact support@bytebase.com and we will assist you to perform the manual upgrade.

🚀 New Features

SQL rollback (detailed guide)

User can now create rollback issue from the original closed issue easily via the UI.

🎄 Experience Enhancement

• Taking backup in a single transaction to make the backup consistent.
• Add alter schema button on the database detail page.
• Add button to allow quickly applying SQL statements to other pipeline stages.
• Hide project quick action list for non-project member.
• Optimize database table list.

🎠 Community

• We have reworked our changelog and blog site to build directly on bytebase.com. This should offer a better browsing experience for our users.
• We published our first technical post on database schema design Choose Primary Key - UUID or Auto Increment Integer? Go check it out.

Update instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from previous veresion, then it requires manual schema change, please contact support@bytebase.com and we will assist you to perform the manual upgrade.

🐞 Important Bug Fixes

MySQL 5.7 compatibility

In the previous version, Bytebase couldn't sync the migration history properly because it used a MySQL 8.0 only feature.

🚀 New Features

Backup and restore (detailed guide)

User can now configure weekly automatic backup for the database. Meanwhile, user can also take manual backup anytime. Later on, User can restore the backup to a new database.

Webhook (detailed guide)

User can now configure webhook to allow Bytebase to post messages to the configured webhook endpoint upon varioius events. Bytebase currently supports following events:

• Issue creation
• Issue status change
• Issue task status change
• Issue info change such as its assignee, title, description
• Issue comment creation

Bytebase also supports following webhook providers:

• Slack
• Discord
• Microsoft Teams
• DingTalk (钉钉)
• Feishu (飞书）
• WeCome (企业微信）

🎠 Community

• Thanks @zhj-hx for providing feedback and helping us troubleshooting the MySQL 5.7 compatibility issue
• Thanks @iczc for the PR.

Update instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from previous veresion, then it requires manual schema change, please contact support@bytebase.com and we will assist you to perform the manual upgrade.

🚀 New Features

• Environment approval policy (detailed guide) - For a particular environment, the workspace Owner or DBA can configure whether the database schema change requires approval.
• Inbox - Added Inbox to the left sidebar. Issue's status change will post to its creator, assignee and subscribers inbox. If there occurs failed task, there will be additional alert symbol.
• Database instance user sync - Bytebase will now periodically sync instance's users and their corresponding grants and display those info on the instance detail page. This helps Bytebase user to quickly recognize who has acccess to an certain instance.

🎠 Community

• We received our first customer review. Thanks @barretlee for the detailed review!
• Our GitHub repository has reached 100 stars at the begining of the week. The user name is @binarysort :)
• We appeared on GitHub Trending during the week and accumulated 500 stars over the week.

Update instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from 0.1.0, then it requires manual schema change, please contact support@bytebase.com and we will assist you to perform the manual upgrade.

🐞 Important Bug Fixes

• MySQL connection leak - In the previous version, when Bytebase does not properly release the connection after finishing connecting the MySQL instance, which will cause MySQL connection pool exhaustation.

🚀 New Features

• External SQL console (detailed guide) - Allow user to configure an external SQL console like phpMyAdmin. If configured, Bytebase will surface the link to the console in the relevant database and table page
• Issue list page - Added a dedicated page to list issues. It supports to filter based on user/project/environment/issue status.
• Project migration history tab - The tab lists the migration history for each database under that project. For each database, Bytebase will list at most 5 most recent migration history, and user can click the database name to view the complete migration history.

🎄 Experience Enhancement

• Added new 403, 404 page

🎠 Community

• We launched our English blog, checkout our launch post.

Update instruction

• For fresh installation, follow https://github.com/bytebase/bytebase#installation.
• If you upgrade from 0.1.0, it requires manual schema change, please contact support@bytebase.com and we will assist you to perform the manual upgrade.

🚀 New Features

• Migration history - Added the migration history to the database detail page. This is applicable to project using either UI or Version Control workflow.
• Table detail page - Added table detail page. This is normally reached via the database detail page. The table detail page displays the basic table info as well as its columns and indexes.

🎄 Experience Enhancement

• Added button to referesh the repository list when configuring the project Version Control workflow.
• Added help doc on how to start a MySQL docker instance.

🎠 Community

• In the first week after we open sourced Bytebase on GitHub, we have added 3 external contributors. We also created and resolved the first issue. Thanks @silentred, @s7v7nislands, @spinningbot for the PR, as well as @IronManZ suggestions on how to improve the MySQL setup guide.

For fresh installation, follow https://github.com/bytebase/bytebase#installation.

We released our first open source version on GitHub. Please checkout our launch post.