• Reference
  • Version · 6.0
  • Change Automation Reference

conditions

Last updated: September 29, 2026

Use the conditions attribute to tag a changeset with the circumstances it is intended for, such as a hotfix, a data fix, or a maintenance window. At runtime, you can control which tagged changesets a command runs using the conditions-filter argument.

Note: The conditions attribute requires Liquibase Secure 5.2.2 or later.

Uses

You can specify a condition as any case-insensitive string, or a comma-separated list of conditions. You can typically use conditions to:

  • Tag changesets with the circumstances they are intended for, such as hotfix or maintenance.

  • Deploy or roll back only the changesets that match the current circumstances.

  • Limit which changesets a checks run operation inspects, without enabling or disabling checks or maintaining separate checks packages and configuration files.

  • Slice deployments across an additional dimension when labels, contexts, teams, and releases are already in use for other purposes.

Syntax

Add the conditions attribute to a changeset in any changelog format. You can specify a single value or a comma-separated list.

Note: In XML changelogs, the attribute name must be lowercase (conditions). In other formats, the attribute name is case-insensitive.

loading

loading

loading

loading

Filtering by conditions

At runtime, pass the --conditions-filter argument to run only the changesets whose conditions attribute matches the filter value. Matching is a straight string comparison with no logical operators. Changesets without a conditions attribute always run, even when a filter is specified. See conditions-filter for matching rules, examples, and supported commands.