> ## 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 2.15.0 - Apr 11, 2024

> Brand new GitOps

## 🔔 Brand New GitOps

*The [new GitOps workflow](/gitops/overview/) is not compatible with the old version, if you need assistance migrating to the new version, please consult us.*

* Use access tokens for authentication.
* Support multiple VCS connectors in a project.
* Support specifying a database group as the target in the VCS connector, automatically applying to all databases in a project by default.
* Deprecate database name templates and latest schema write-back.

## 🚀 New Features

* Support [Vault](/get-started/instance/#hashicorp-vault) as an external data source for database secrets.
* Support Apache Hive.
* Add one-time data export issue type.

## 🎄 Enhancements

* Improve SQL Editor UI/UX.
* Add SQL review rules for PostgreSQL：
  * Detect non-transactional statements.
  * Require using NOT VALID when creating foreign keys.

## 📰 Fresh Off the Press

* In the realm of database management, PostgreSQL 🐘 stands out for its robustness and flexibility. Yet, as developers 🧑‍💻 tackle the complexities of modern application development, there's room for enhancement to make their processes more efficient. [This article](https://www.bytebase.com/blog/features-i-wish-postgres-had/) outlines the most sought-after PostgreSQL features.

* Is it worthwhile to migrate to AlloyDB, ☁️ Google Cloud's fully managed PostgreSQL-compatible database service? 🧐. You may find the answer after reading [Understanding Google Cloud AlloyDB Pricing](https://www.bytebase.com/blog/understanding-google-alloydb-pricing/).

## ⚙️ 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.*