Shipped · DevOps and infrastructure

What liquibase/liquibase shipped

The public repository of Liquibase · github.com/liquibase/liquibase

Written by FoxPlug from the repository's own releases; not affiliated with Liquibase. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/liquibase/liquibase; Liquibase did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for liquibase, free

Week of October 19, 2026

What shipped

Why it matters

This week fixes several failures that hit people running updates and snapshots in real environments: a transactional gap between a changeset and its DATABASECHANGELOG row, a lock row that stays locked after a process dies, slow no-op runs, and snapshot failures on PostgreSQL real columns. It also adds an opt-in PostgreSQL lock option and improves SQL logging so runs are easier to follow.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: changesets and their DATABASECHANGELOG updates now commit atomically, an opt-in PostgreSQL advisory lock service, faster no-op runs, SQL logged at liquibase.sql.logLevel, and PostgreSQL REAL default snapshot fixes.

Post for LinkedIn

This week in Liquibase: a changeset and its DATABASECHANGELOG update now commit atomically for update and rollback, so a mid-update failure no longer leaves them out of step. An opt-in PostgreSQL session lock service avoids the LOCKED row left behind when a process dies. Slow no-op runs since 4.30 are fixed, SQL through the JdbcExecutor query and update paths is logged at liquibase.sql.logLevel, PostgreSQL REAL expression defaults are preserved in snapshots, and the Snowflake column remarks view check is scoped to the target schema.

Week of October 5, 2026

What shipped

Why it matters

This week brought several correctness fixes for everyday migration runs. Concurrent updates no longer leave stale changelog locks behind, and updateCount and updateSql no longer block on the lock when nothing is pending. CSV loading with leading comments or blank lines now reads the header correctly, and H2 users get an accurate columnExists result.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: changelog lock fixes for concurrent updates and for updateCount/updateSql, CSV loadData header parsing with comments or blank lines, H2 columnExists with catalogName, and Firebird sequence startValue and incrementBy.

Post for LinkedIn

This week in Liquibase: concurrent updates no longer leave each other's changelog locks set, and updateCount and updateSql now acquire the changelog lock lazily after the fast-check so a stale lock does not block startup when nothing is pending. CSV loading now skips leading comment and blank lines before reading the header, fixing column-count mismatch failures. columnExists returns correctly on H2 when catalogName is set, and Firebird now supports sequence startValue and incrementBy. Release tooling also got fixes: the dry run publishes to Nexus, and a PR gate fails when the release approval gate can be bypassed.

Week of September 21, 2026

What shipped

Why it matters

This week consolidated artifact storage by migrating from legacy S3 buckets to Cloudflare R2, removing intermediate copy steps so that javadocs and release assets serve directly from their final destination. The changes also fix release workflow dispatch gates and improve Docker image security scanning rules.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Release infrastructure now publishes javadocs and OSS assets directly to Cloudflare R2. Removed legacy S3 sync steps and fixed dry-run release gates. Docker security scanning rules now match Grype behavior.

Post for LinkedIn

This week's infrastructure improvements streamline how Liquibase publishes its artifacts. We've migrated javadocs and OSS release assets to Cloudflare R2, eliminating legacy S3 bucket dependencies and removing unnecessary copy-on-read bridges. We also fixed release workflow gates to unblock dispatched dry runs and improved Docker security scanning to correctly identify unfixed vulnerabilities.

Week of September 14, 2026

What shipped

Why it matters

This week's changes harden the release and build infrastructure by establishing traceable commits for releases, fixing gate logic that was blocking releases, cleaning up stale artifacts from public registries, and removing security risks from orphaned workflows. These improvements make the release process more reliable and secure.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Release infrastructure hardening: pinned commits for releases, fixed validation gates, cleaned up orphaned artifacts, and removed unreachable workflows holding inherited secrets.

Post for LinkedIn

This week we strengthened Liquibase's release and build infrastructure with several critical improvements: releases now build from pinned commits instead of operator-supplied IDs, establishing full traceability; the release validation gate was fixed to avoid counting its own runs; package cleanup now removes all branch-named SNAPSHOT versions from public registries; and we removed an unreachable workflow that held inherited secrets. These changes make our release process more reliable and secure.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-10-27.

Is this your repo? Ask us to remove this page.