Hey everybody!
Liquibase Secure 5.2 is live, and it brings a meaningful shift for anyone whose teams are using Cursor, Claude, GitHub Copilot, or other AI assistants to help write database changes.
AI can now create database changes in seconds. Traditional controls, built for a slower world of tickets, manual reviews, and after-the-fact audit trails, weren’t designed for that. 5.2 introduces what we’re calling Agent Safe Governance to close that gap.
The principle is simple. AI can help create a database change. It cannot bypass the checks, approvals, audit trails, schema lineage, drift detection, and recovery controls enterprises require before production.
Liquibase MCP server
The new Liquibase MCP server connects AI-assisted workflows directly to Liquibase Secure. Developers and AI assistants can create Liquibase-formatted changelogs, schema updates, rollback logic, and AI-generated DDL, and every artifact flows into the same governed pipeline as human-authored change.
Change Intelligence and schema lineage
Change Intelligence gives teams a single source of truth for every database change.
It helps teams see:
-
What changed
-
Who or what created it
-
Where it ran
-
Whether controls were followed
-
How the schema evolved over time
-
Whether drift exists
-
What evidence is available for audit or investigation
Policy checks and drift detection
Pre-deployment policy checks block risky operations, enforce standards, support separation of duties, and validate compliance requirements before changes reach production. Drift detection catches what slips through, including manual fixes, emergency updates, shadow changes, and AI-assisted changes that bypass governed workflows.
Expanded database support
5.2 deepens support for complex enterprise database estates with new capabilities for Teradata, MongoDB, and DynamoDB, on top of the 65+ databases already supported across relational, NoSQL, cloud, and legacy systems.
Why this matters
96.5% of organizations already let AI or LLMs interact with production databases (2026 State of Database Change Governance Report). Most enterprises are running AI-era velocity on pre-AI controls. 5.2 is built to close that gap with one consistent control model for every database change, human or AI.
Learn more:
Launch blog: Liquibase Secures Your Database Changes. Human or AI. | Liquibase Secure
Release notes: 5.2 Secure Release Notes - Liquibase
Webinar on June 24: Agent Safe Governance: Govern AI-Generated Database Change | Liquibase
Questions and feedback are always welcome!