- Reference
- Version · 6.0
- Change Automation Reference
keywords
Last updated: September 29, 2026
Use the keywords attribute to tag a changeset with short terms that describe your own filtering dimension, such as a business domain, a compliance category, or an application area. At runtime, you can control which tagged changesets a command runs using the keywords-filter argument.
Note: The keywords attribute requires Liquibase Secure 5.2.2 or later.
Keep each keyword to a short, single term, like a tag. The value is split on commas, so it is not suitable for narrative notes or sentences.
Uses
You can specify a keyword as any case-insensitive string, or a comma-separated list of keywords. You can typically use keywords to:
Tag changesets with short terms that describe your own filtering dimension, such as
hotfixorcompliance.Deploy or roll back only the changesets that match one or more keywords.
Limit which changesets a
checks runoperation inspects, without enabling or disabling checks or maintaining separate checks packages and configuration files.Slice deployments across an additional dimension when
labels,contexts,teams, andreleasesare already in use for other purposes.
Syntax
Add the keywords 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 (keywords). In other formats, the attribute name is case-insensitive.
Filtering by keywords
At runtime, pass the --keywords-filter argument to run only the changesets whose keywords attribute matches the filter value. Matching is a straight string comparison with no logical operators. Changesets without a keywords attribute always run, even when a filter is specified. See keywords-filter for matching rules, examples, and supported commands.