- Reference
- Version · 6.0
- Change Automation Reference
releases
Last updated: September 29, 2026
Use the releases attribute to tag a changeset with the release or releases it ships in. At runtime, you can control which tagged changesets a command runs using the releases-filter argument.
Note: The releases attribute requires Liquibase Secure 5.2.2 or later.
Uses
You can specify a release name as any case-insensitive string, such as v1.0 or 2026-q3, or a comma-separated list of release names. You can typically use releases to:
Tag each changeset with the release or releases it ships in, such as
v1.0orv1.1.Deploy only the changesets that belong to a specific release, or to a set of releases.
Roll back the changesets from one release without affecting changesets from other releases.
Limit which changesets a
checks runoperation inspects to the current release.
Syntax
Add the releases 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 (releases). In other formats, the attribute name is case-insensitive.
Filtering by releases
At runtime, pass the --releases-filter argument to run only the changesets whose releases attribute matches the filter value. Matching is a straight string comparison with no logical operators. Changesets without a releases attribute always run, even when a filter is specified. See releases-filter for matching rules, examples, and supported commands.