- Reference
- Version · 6.0
- Change Automation Reference
license status
Last updated: September 29, 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. |
| 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 reports Source: local license file, pre-6 format. Liquibase also prints at startup that the license predates the 6 format, was verified with the previous format, and remains valid. That is the confirmation an upgrading installation needs.
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. |
|
|