# Install flyway with Homebrew

Database version control to control migrations. Version 13.1.0 via Homebrew; verified 2026-07-30.

## Install

```sh
sudo av install brew:flyway
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install flyway
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:flyway
- **Package manager:** Homebrew
- **Version:** 13.1.0
- **Source summary:** Database version control to control migrations
- **Homepage:** <https://www.red-gate.com/products/flyway/community/>
- **Repository:** <https://github.com/flyway/flyway>
- **Last updated:** 2026-07-30T12:27:27Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- flyway (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 13.1.0
## Project history and usage

Redgate Flyway is a database migration and schema versioning tool for command-line, API, Maven, Gradle, Docker, and desktop workflows. It applies versioned migrations, records them in a schema history table, and is used to bring database change management into application-style CI/CD pipelines.

### Project history

The open-source repository identifies Flyway as a Redgate project and carries copyright from 2010 through 2026. The README emphasizes a simple, focused migration model and lists support across Windows, macOS, Linux, Docker, Java, Maven, and Gradle.

Redgate documentation presents Flyway as part of a wider product family that includes Flyway Command Line, Flyway Desktop, APIs, build-tool integrations, and Redgate editions. The GitHub README also notes that Flyway is a registered trademark of Boxfuse GmbH owned by Red Gate Software Ltd.

### Adoption history

Flyway's adoption is tied to the rise of database DevOps: its own documentation says it extends DevOps to databases, automates database deployments, and is commonly used from the command line in CI/CD systems. The README lists support for 50-plus DBMS products and many community or third-party integrations, including Spring Boot, SBT, Ant, Grails, Play, DropWizard, Grunt, Griffon, and Ninja.

### How it is used

The standard workflow is to create ordered SQL, Java, or scripting migrations, run Flyway against a database, and let it create or update the `flyway_schema_history` table as migrations are applied. It can be used directly through the CLI, embedded through the Java API, or driven through Maven and Gradle.

### Why package nerds care

Flyway matters to package ecosystems because it is both a standalone CLI and a Java library/plugin stack. It bridges application release tooling and mutable database state, so packaging has to serve local developer installs, CI runners, containers, build plugins, and enterprise editions without confusing the open-source command-line engine with Redgate's commercial surfaces.

### Timeline

- 2010: The Flyway open-source repository's copyright period begins.
- 2021: Redgate Flyway documentation was published in its current documentation space.
- 2022: Redgate published the Flyway Engine release-notes page in the current documentation system.
- 2024: The GitHub release stream included Flyway 10.x releases.
- 2026: Redgate documentation listed Flyway 12.10.0 as a current engine release.

### Related projects

- Related official surfaces include Flyway Desktop, Flyway Command Line, Flyway Java API, the Maven and Gradle plugins, flyway-community-db-support, and Redgate's commercial Flyway editions.

### Sources

- <https://api.github.com/repos/flyway/flyway/releases?per_page=100>
- <https://documentation.red-gate.com/fd/release-notes-for-flyway-engine-179732572.html>
- <https://documentation.red-gate.com/flyway>
- <https://documentation.red-gate.com/flyway/getting-started-with-flyway>
- <https://github.com/flyway/flyway>
- <https://raw.githubusercontent.com/flyway/flyway/main/README.md>


## Security Notes

No matching local secret-handling manifest was found for flyway. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ./flyway.toml, ./flyway.conf, ~/flyway.conf, <flyway-install-dir>/conf/flyway.conf

## Credential files

- Unix: ~/flyway.conf

## Combined YAML source

View the package source record on GitHub. [combined/flyway.yml](https://github.com/automic-vault/db/blob/main/combined/flyway.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation