• Reference
  • Version · 6.0
  • Change Automation Reference

teams

Last updated: September 29, 2026

Use the teams attribute to tag a changeset with the team or teams responsible for it. At runtime, you can control which tagged changesets a command runs using the teams-filter argument.

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

Uses

You can specify a team name as any case-insensitive string, or a comma-separated list of team names. You can typically use teams to:

  • Tag each changeset with the team or teams responsible for it, such as dba or security.

  • Deploy or roll back only the changesets that belong to specific teams.

  • 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 and contexts are already in use for other purposes.

Syntax

Add the teams 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 (teams). In other formats, the attribute name is case-insensitive.

loading

loading

loading

loading

Filtering by teams

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