Hi all,
I’ve submitted PR #6251 for TRUNK-6634 — Liquibase changesets marked dbms="mysql" are silently skipped on MariaDB 11+ (which dropped the 5.5.5- version prefix, so Liquibase now detects it as MariaDB rather than MySQL). This leaves schema and core data missing on MariaDB 11 deployments.
The open question on the ticket was whether editing historical changesets breaks checksum validation on existing databases. I measured it against Liquibase 4.32.0 (v8 and v9): changing the dbms attribute or a <dbms> precondition does not change a changeset’s checksum, but adding a <modifySql> block does. The PR follows that result — extending dbms="mysql,mariadb" in place where it’s checksum-safe (253 changesets), and adding dedicated mariadb-only changesets where it isn’t. A new test pins all 718 historical checksums so this can’t silently regress.
As a first-time contributor my CI workflows show “Action required” — could a maintainer approve the run and take a look when there’s a moment? SonarCloud has already passed clean.
This is complementary to the existing PR #6109; the checksum findings apply to evaluating either approach.
Thanks!