- Reference
- Version · 6.0
- Change Automation Reference
labels
Last updated: September 29, 2026
Labels are tags you add to changesets in your changelog to describe what each changeset is for, such as a particular feature or version. You can specify a label name as any case-insensitive string. At runtime, you can control which labeled changesets a command runs using the label-filter argument.
Labels work best when the changeset author can simply enumerate or describe what a changeset is used for. The complexity of deciding which changesets to run is left to the deployment manager or person executing the changesets, who selects them at runtime with a filter expression. Labels are similar to contexts, which you can use to specify other tags, such as development environments.
Uses
You can typically use labels to:
Manage and track your deployments.
Apply complex logic to filter the changesets eligible for deployment.
Mark changesets based on features and then selectively apply those features at the execution time instead of using version control branches.
Use different languages for marking changesets. For example, you can mark your changesets both with Spanish and English.
Assign ticket numbers to particular changesets to track and identify their purpose, such as JIRA ticket numbers
include and includeAll labels
You can specify the labels attribute in include and includeAll tags. If specified, the given label is added to all changesets in the included file(s).
Syntax
Filtering labels
At runtime, use the label-filter argument to determine which changesets run based on their labels. The label filter is a logical expression that supports AND, OR, !, parentheses, and the @ strict-matching operator. See label-filter for the full expression syntax and examples.
If a changeset doesn't have a label, it will always run, even when a label filter is specified, unless the filter uses the @ operator. If you make a deployment without specifying any labels in the label filter, all changesets will run.
Liquibase also provides filter arguments for other changeset attributes. Each argument filters on its own attribute:
Argument | Filters on | Matching |
| Logical expressions: | |
| Comma-separated list. Expression logic is set on the changeset. | |
| Straight string match. Comma-separated list matches any value. As of Secure 6.0, supports the @ strict-matching operator. | |
| Straight string match. Comma-separated list matches any value. As of Secure 6.0, supports the @ strict-matching operator. | |
| Straight string match. Comma-separated list matches any value. As of Secure 6.0, supports the @ strict-matching operator. | |
| Straight string match. Comma-separated list matches any value. As of Secure 6.0, supports the @ strict-matching operator. |
Note: The teams, releases, keywords, and conditions attributes and their filters require Liquibase Secure 5.2.2 or later.