Task
Version · 6.0
Deliver

RequireChangesetIDisUUID

Last updated: July 13, 2026

This check alerts you when a changeset ID does not follow the 8-4-4-4-12 pattern of UUID or GUID.

Uses

Property	Value
Liquibase version required	4.12.0+
Scope (--checks-scope)	changelog
Default status	disabled
Default severity (exit code)	0 ("INFO")
Customizable settings	No (static)

Use the check to notify you when the 8-4-4-4-12 pattern of UUID or GUID is not followed when creating a changeset ID. The 8-4-4-4-12 UUID or GUID pattern is straightforward, but also easy to mistype, which can cause failures in other tools down your chain which count on a valid UUID or GUID. This policy check, like other checks, can be configured with a severity level which returns an exit code designed to stop automated jobs, giving your team time to make sure simple mistakes are not deployed.

Procedure

Enable

This check is disabled by default. To enable it, run the checks enable command:

liquibase checks enable --check-name=<string>

To run the check, use the checks run command.

liquibase checks run --check-name=<string>

stages:
  Default:
    actions:
      - type: liquibase
        command: checks run
        cmdArgs: {check-name: <string>}

liquibase checks run --check-name=<string>

stages:
  Default:
    actions:
      - type: liquibase
        command: checks run
        cmdArgs: {check-name: <string>}

Note: For flow files you'll need to run liquibase flow to apply your changes.

Example output

Short Name	Category	Description	Customization	Status	Severity	Scope	Type
RequireChangesetIDisUUID	Metadata Content	Enforces that all changeset IDs use the standard UUID or GUID format with the 8-4-4-4-12 hyphenated pattern, promoting globally unique changeset identifiers that prevent collisions and improve traceability across distributed teams and multiple changelog files.	<None>	enabled	0	changelog	sql, xml, yaml, json

Liquibase command 'checks show' was executed successfully.

PreviousPatternANotPrecededByPatternB NextRollbackRequired