# A few thoughts on Secure 6.0

**URL:** <https://forum.liquibase.org/t/a-few-thoughts-on-secure-6-0/10958>\
**Category:** General Discussion\
**Created:** [September 30, 2026, 4:16pm UTC](https://forum.liquibase.org/t/a-few-thoughts-on-secure-6-0/10958 "2026-09-30T16:16:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pete](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/pete/32/184_2.png) [@Pete](https://forum.liquibase.org/u/Pete)\
**Post date:** [September 30, 2026, 4:16pm UTC](https://forum.liquibase.org/t/a-few-thoughts-on-secure-6-0/10958/1 "2026-09-30T16:16:21Z")

</div>

We released Liquibase Secure 6.0 today. Rather than go through everything in the release, I thought I’d share a little about why we built it.

When we started Liquibase, a lot of the problem was simply getting database changes out of manual processes. Make the changes repeatable. Put them in version control. Automate them along with the application.

We’ve spent a lot of years working with teams doing that now, and one thing we’ve learned is that things get more complicated when Liquibase becomes a standard across a large organization.

At that point, it’s not just whether you can automate a database change. People start asking what’s changing across all these databases. Are teams following the standards we agreed on? What happened with that deployment yesterday? Who gets to change the rules?

Those questions are behind a lot of what we built in 6.0.

Change Intelligence is the biggest new piece. It gives teams a way to see deployment activity, policy outcomes, drift, and failures across their database estate. We also rebuilt the policy management experience and added role-based access control.

There’s more in the release, of course. But the bigger direction for us is making Liquibase work not just as a way to automate database change, but as a way for an organization to manage that change consistently and safely at scale.

AI makes this more important because there’s more change coming from more places. I don’t think it fundamentally changes the problem though. Whether a change starts with a human developer, their coding assistant, or an agent, you still need to know what happened and have some control over how it gets executed, especially in production.

Happy to answer questions here. What’s changed under the hood, migration from 5.x, what’s next, etc.

Pete

Learn more [here](https://www.liquibase.com/blog/introducing-liquibase-secure-6-0).

---

<div class="post-metadata">

**Author:** ![Pete](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/pete/32/184_2.png) [@Pete](https://forum.liquibase.org/u/Pete)\
**Post date:** [September 30, 2026, 4:15pm UTC](https://forum.liquibase.org/t/a-few-thoughts-on-secure-6-0/10958/2 "2026-09-30T16:15:19Z")

</div>