# Install golang-migrate with Homebrew, dnf, Nix, scoop, apt Database migrations CLI tool. Version 4.19.1 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:golang-migrate ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install golang-migrate ``` Evidence: local Homebrew formula metadata ### Linux - dnf (92%): ```sh sudo dnf install migrate ``` Evidence: Fedora Rawhide package metadata: migrate from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst - Nix (92%): ```sh nix profile install nixpkgs#migrate ``` Evidence: nixpkgs package indexes: pkgs/by-name/mi/migrate/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt (92%): ```sh sudo apt install python-migrate-doc ``` Evidence: Ubuntu 24.04 LTS package indexes: python-migrate-doc from https://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.gz ### Windows - Scoop (92%): ```sh scoop install main/migrate ``` Evidence: Scoop official bucket manifest trees: bucket/migrate.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:golang-migrate - **Package manager:** Homebrew - **Package manager page:** - **Version:** 4.19.1 - **Source summary:** Database migrations CLI tool - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - migrate (cli) - migrate (alias) ## Build dependencies - go ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 4.19.1 - Local data: ok - Upstream repository: https://github.com/golang-migrate/migrate - Upstream latest detected: v4.19.1 (current) - info: No package-manager update timestamp was available. ## Project history and usage golang-migrate is a Go database migration project distributed as both a CLI and a Go library. It applies ordered migration files from source drivers to database drivers, deliberately keeping database drivers simple while centralizing migration logic in the core package. ### Project history The project traces back to `mattes/migrate`, a database migration repository created in 2014. The maintained `golang-migrate/migrate` repository was created in January 2018 and states that it was forked from `mattes/migrate`. The fork preserved the core CLI/library model while continuing the driver architecture. Its README documents a broad matrix of database drivers, including PostgreSQL, MySQL/MariaDB, SQLite, SQL Server, Cassandra/ScyllaDB, ClickHouse, MongoDB, CockroachDB, and cloud-oriented sources such as GitHub, GitLab, S3, and Google Cloud Storage. The project standardized on Go module import paths for v4 and explicitly marks v3 as unsupported in its README. That version boundary matters because many Go projects embed migration support directly in their own binaries rather than only shelling out to the CLI. ### Adoption history golang-migrate became a common Go ecosystem migration tool because it works both as a standalone `migrate` binary and as an importable library. The README points to packagecloud deb packages, Docker images, GitHub releases, and Go documentation, while the batch input records Homebrew, Fedora, Nix, Scoop, and other package-manager entries. The maintained fork's GitHub repository had over 18,000 stars and more than 1,500 forks in the 2026 GitHub API snapshot used for this batch, making it one of the better-known Go-native database migration tools. ### How it is used The standard workflow is to create paired up/down SQL files with `migrate create`, then run them with a source such as `file://path/to/migrations` and a database URL. The getting-started guide emphasizes running migrations up, down, and up again before committing them. Operationally, golang-migrate is intentionally explicit: the README says the CLI has no config search paths, no config files, and no magic environment-variable injection. Users pass source and database URLs directly, and database credentials normally live in those URLs or in caller-managed secret handling rather than in a tool-owned credentials file. The getting-started guide highlights dirty database states, force operations, idempotent migrations, transaction wrapping, and database locking when multiple app instances may run migrations. Those warnings are why package users often treat `migrate` as deployment infrastructure rather than a casual development helper. ### Why package nerds care For package nerds, golang-migrate is the archetypal Go single-binary infrastructure tool: it can be installed from Homebrew, run from Docker, vendored as a library, or baked into a release artifact. The driver split also makes downstream builds interesting, because packagers and application authors decide which database/source drivers to include. Its significance is also cultural: it represents the Go preference for explicit URLs, small binaries, and predictable failure over framework-managed migration magic. That makes it popular in CI pipelines and container entrypoints where reproducibility beats convenience. ### Timeline - 2014: `mattes/migrate` repository created for database migrations in Go. - 2017: `mattes/migrate` v3 preview releases published. - 2018: `golang-migrate/migrate` repository created as a fork of `mattes/migrate`. - 2018: `golang-migrate/migrate` v3.1.0 and later v3 releases published. - 2019-2026: v4 import path and driver ecosystem documented as the supported line; v3 documented as unsupported. ### Related projects - `mattes/migrate` is the direct upstream ancestor named by the maintained repository. - The README points users coming from other migration systems to `migradaptor`, and it links broader database-tool alternatives through Awesome Go. - Database and source drivers connect golang-migrate to PostgreSQL, MySQL/MariaDB, SQLite, MongoDB, ClickHouse, SQL Server, GitHub, GitLab, S3, and Google Cloud Storage workflows. ### Sources - - - - - - ## Security Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool signal ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** golang-migrate - **Version Scheme:** 0 - **Revision:** 0 - **Head Version:** HEAD - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** head, stable ## Other Package-Manager Records - Nix - migrate: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/mi/migrate/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt - python-migrate-doc - 0.13.0-0ubuntu2: installed executable or alias match | Ubuntu 24.04 LTS package indexes: python-migrate-doc from https://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.gz | Database schema migration for SQLAlchemy - doc | https://github.com/openstack/sqlalchemy-migrate - Ubuntu apt - python3-migrate - 0.13.0-0ubuntu2: installed executable or alias match | Ubuntu 24.04 LTS package indexes: python3-migrate from https://archive.ubuntu.com/ubuntu/dists/noble/main/binary-amd64/Packages.gz | Database schema migration for SQLAlchemy - Python 3.x | https://github.com/openstack/sqlalchemy-migrate - dnf - migrate - 4.19.1-4.fc44: installed executable or alias match | Fedora Rawhide package metadata: migrate from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst | Go database migrations library and program | https://github.com/golang-migrate/migrate - Scoop - main/migrate: installed executable or alias match | Scoop official bucket manifest trees: bucket/migrate.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [go](https://www.automicvault.com/pkg/brew/go/) - Build dependency declared by Homebrew. - [liquibase](https://www.automicvault.com/pkg/brew/liquibase/) - Shares av.db curated category or tags: cli, database, developer-tools, migrations, schema. - [sql-migrate](https://www.automicvault.com/pkg/brew/sql-migrate/) - Shares av.db curated category or tags: cli, database, developer-tools, go, migrations. - [jet](https://www.automicvault.com/pkg/brew/jet/) - Shares av.db curated category or tags: cli, database, developer-tools, go. - [sqlboiler](https://www.automicvault.com/pkg/brew/sqlboiler/) - Shares av.db curated category or tags: cli, database, developer-tools, go. - [sqlc](https://www.automicvault.com/pkg/brew/sqlc/) - Shares av.db curated category or tags: cli, database, developer-tools, go. - [sqlcmd](https://www.automicvault.com/pkg/brew/sqlcmd/) - Shares av.db curated category or tags: cli, database, developer-tools, go. - [chdig](https://www.automicvault.com/pkg/brew/chdig/) - Shares av.db curated category or tags: cli, database, developer-tools. - [dbhash](https://www.automicvault.com/pkg/brew/dbhash/) - Shares av.db curated category or tags: cli, database, developer-tools. ## Combined YAML source View the package source record on GitHub. [combined/golang-migrate.yml](https://github.com/automic-vault/db/blob/main/combined/golang-migrate.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph