# Installer liquibase-community avec Homebrew Cask

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de liquibase-community pour les workflows d'agents IA.

## installation

```sh
sudo av install cask:liquibase-community
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew Cask (100%):

```sh
brew install --cask liquibase-community
```

  Preuve: local Homebrew cask metadata

## Faits du paquet

- **Clé du paquet:** cask:liquibase-community
- **Gestionnaire de paquets:** Homebrew Cask
- **Version:** 5.0.3
- **Résumé source:** Library for database change tracking
- **Page d'accueil:** <https://www.liquibase.com/community>
- **Dernière mise à jour:** 2026-05-15T13:47:05Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- liquibase (binaire)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 5.0.3
## Historique du projet et usages

Liquibase Community is the community-supported distribution of Liquibase, a database change management tool that records database changes in changelogs, applies undeployed changesets, and tracks execution in tables such as DATABASECHANGELOG.

### Historique du projet

Nathan Voxland founded the Liquibase open-source project in 2006 to make database changes easier to track. The project grew from a Java-oriented schema change tool into a cross-database migration and deployment tool with a command line, libraries, build-tool integrations, and commercial governance features.

The official GitHub repository is the main Liquibase source tree and is organized around Java and Groovy code. Liquibase documentation describes Community as a community-supported tool for managing database change, while the same documentation site also separates commercial Liquibase Secure material.

### Historique d'adoption

Liquibase became popular because it treated database schema changes as versioned artifacts that could travel with application code. Changelogs in SQL, XML, YAML, and JSON, plus checksums and the DATABASECHANGELOG table, made it useful in CI/CD, Java application delivery, and regulated database deployment workflows.

The Liquibase company page describes the project as a de facto standard for database change management. Its GitHub repository topics and docs show sustained use around MySQL, Oracle, SQL Server, DB2, MariaDB, DevOps, continuous delivery, and database migrations.

### Modes d'utilisation

Community users write changelogs, identify changesets by id and author, and run commands such as update, rollback, diff, and generate-changelog against target databases. Liquibase stores applied-change metadata in DATABASECHANGELOG and uses checksums to detect unexpected changes to already-deployed changesets.

The Homebrew cask packages the Liquibase Community distribution path, with a cask install command and a Liquibase-hosted archive. In this batch it differs from the Homebrew formula: the cask record names Liquibase Community and version 5.0.3, while the formula record names liquibase and version 4.33.0.

### Pourquoi les passionnés de paquets s'y intéressent

Liquibase is package-nerd interesting because it is both a library and an operations CLI: the package must bring along Java expectations, JDBC driver workflows, config-file conventions, and a CLI that often runs inside release automation.

The Community cask is significant as a vendor-distribution style Homebrew artifact. It points users to Liquibase's Community product surface and download archive rather than merely building a formula around the open-source source tree.

### Chronologie

- 2006: Nathan Voxland founded the Liquibase open-source project.
- 2010s: Liquibase became a common database migration tool in Java and DevOps workflows, with changelog formats beyond XML and command-line/build-tool integrations.
- 2020: The company behind commercial Liquibase tooling operated under the Liquibase brand, aligning the company identity with the open-source project.
- 2025: Liquibase documentation for Community 5.0 described Community as the community-supported tool for managing database change.
- 2026: The Homebrew cask record for this batch identifies Liquibase Community 5.0.3 and a Liquibase-hosted download archive.

### Related projects

- Flyway is the most commonly compared database migration tool; both are package-manager fixtures for teams that want repeatable database deployments.
- Liquibase also sits near JDBC drivers, Maven and Gradle integrations, Docker images, CI/CD systems, and database-native tooling used for schema comparison, rollback, and deployment governance.

### Sources

- <https://docs.liquibase.com/>
- <https://docs.liquibase.com/community/user-guide-5-0-3/what-is-a-changelog>
- <https://docs.liquibase.com/secure/user-guide-5-2/what-is-the-databasechangelog-table>
- <https://formulae.brew.sh/cask/liquibase-community>
- <https://formulae.brew.sh/formula/liquibase>
- <https://github.com/liquibase/liquibase>
- <https://www.liquibase.com/company/leadership>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour liquibase-community. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## 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: ./liquibase.properties, $LIQUIBASE_HOME/examples/<sql|xml|yaml|json>/liquibase.properties

## Credential files

- Unix: ./liquibase.properties, path supplied with --driver-properties-file
## Autres enregistrements de gestionnaires de paquets

- Nix - liquibase: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/li/liquibase/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- apk - liquibase - 4.9.1-r0: installed executable or alias match | Alpine Linux edge package indexes: liquibase from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Source Control for your Database | https://www.liquibase.org/
- apk - liquibase-doc - 4.9.1-r0: installed executable or alias match | Alpine Linux edge package indexes: liquibase-doc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Source Control for your Database (documentation) | https://www.liquibase.org/
- Chocolatey - liquibase: installed executable or alias match | Chocolatey community package catalog: liquibase from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','lftp'
- Scoop - main/liquibase: installed executable or alias match | Scoop official bucket manifest trees: bucket/liquibase.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - Liquibase.Liquibase: installed executable or alias match | Windows Package Manager source index: Liquibase.Liquibase from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/liquibase-community.yml](https://github.com/mxcl/pkgdb/blob/main/combined/liquibase-community.yml)


## Sources

- pkg.so package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
