• 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? Status and Commands say so directly.

  • Which source won? A node can have a file, an endpoint, and a key all configured. Source names 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

Status

valid when the artifact verified and the term has not passed.

Commands

allowed when Secure capabilities will run.

Source

Which of the three sources was used, and where that value came from.

Issued to

The name the license was issued to.

License expires

The end of the term.

Trusted verify keys

Each key that can verify a license, with where it came from.

A 5.x license reports Source: local license file, pre-6 format.

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

Reason

Why no license is in effect.

Code

The error code. LB-LIC-0021 is listed in Error codes and exit codes.

What to do

The three properties that would license this installation.

Source

none configured when nothing was found.

PreviousExecute-sqlNextList-locks