- Reference
- Version · 6.0.2
- Change Automation Reference
license status
Last updated: November 17, 2026
Reports the license Change Automation resolved for this installation: whether it is valid, where it came from, when it expires, and which keys verified it.
Uses
Run it to answer three questions that are otherwise guesswork.
Is this node licensed?
StatusandCommandssay so directly.Which source won? A node can have a file, an endpoint, and a key all configured.
Sourcenames the one Liquibase actually used.Why was a command refused? The unlicensed output carries the reason, the error code, and the remediation.
The command reads configuration and reports. It changes nothing.
Syntax
liquibase license status
Output when licensed
Field | What it reports |
|
|
|
|
| Which of the three sources was used, and where that value came from. |
| Shown only when an endpoint is configured, it supplied no license, and the license configured on this node was tried instead. It gives the reason the endpoint was skipped. |
| The name the license was issued to. |
| The end of the term. |
| Each key that can verify a license, with where it came from. |
A 5.x license key reports Source: pre-6 license key (from …), where the parentheses name the setting the key was read from, such as Environment variable 'LIQUIBASE_LICENSE_KEY'. A 5.x key saved in a file that liquibase.licenseFile points to reports the file instead, for example Source: License file '/opt/liquibase/license.key', pre-6 format.
When an endpoint is configured and does not supply a license, for example because it cannot be reached, it refuses the request, or its license fails verification, Liquibase uses the license configured on the node. Source then names that license, and License endpoint says why the endpoint was skipped:
License endpoint: The license endpoint https://licenses.example:8443 refused this request because liquibase.platform.apiKey does not hold a key it accepts. Liquibase falls back to the license configured on this node.
Every command prints the same sentence on STDERR as a WARNING: line before any other output, including --version and --help. It is not written to --log-file. In an embedded run, such as the Maven plugin or Spring, it is logged at WARNING instead.
The release signing key is built into the Liquibase build, so Trusted verify keys lists it with no configuration on your part.
Output when unlicensed
Field | What it reports |
| Why no license is in effect. |
| The error code. |
| The three properties that would license this installation. |
|
|