- Task
- Version · 6.0
- Deliver
Skip or exclusively inspect changesets with Checks Targeting
Last updated: September 29, 2026
Overview
Note: Checks Targeting requires Liquibase Secure 6.0 or later and a valid Liquibase Secure license.
Checks Targeting lets you set persistent rules so a policy check either treats certain changesets as approved exceptions (exempt) or inspects only certain changesets (restrict), without disabling the check or editing your changelog. This guide shows how to create, review, and remove those rules. For the concepts, see What is Checks Targeting?.
Before you begin
Liquibase Secure 6.0 or later with a valid license.
Policy checks already configured (you have a checks settings file and can run
checks run).The changesets you want to target carry at least one of the
teams,releases,keywords,conditions,labels, orcontextsattributes. Set them on individual changesets, or across a changelog with Apply changeset attributes in bulk with modifyChangeSets.
Procedure
Decide which changesets to exempt or restrict
Choose an exempt rule to let matched changesets be inspected without failing the run. They still appear in the report as
INFO.Choose a restrict rule to make a check inspect only the matched changesets and skip all others.
Note: A rule can set more than one filter. Values within one filter are a comma-separated OR list, and separate filters combine with AND. A leading @ on a value is accepted but does nothing, because a filter always matches strictly. What is Checks Targeting? covers the full matching behavior.