- Concept
- Release notes
6.0.2 Secure release notes
What's new
Liquibase Secure 6.0.2 is a maintenance and feature update to Liquibase Secure 6.0. It makes deployments easier to control and more reliable, gives you more control over who can see and change what, and keeps secrets out of more places.
The main highlights: decorate-sql is now available for Oracle and SQL Server only. It turns raw SQL files into Liquibase-managed changelogs and accepts one or more folders in a single run, so a pipeline can decorate an entire release folder in one step. On the server side, Liquibase Secure Server can now run on your own PostgreSQL 17 database, Change Governance gains finer-grained permissions and a Governance Lead template, and personal access tokens replace per-user API keys.
Liquibase Secure 6.0.2 is available now. Download Liquibase Secure 6.0.2.
What's new at a glance
Change Intelligence reads operation reports from Amazon S3 and Azure Blob Storage, reconciles policy check metrics with the CLI, and shows a per-command result for every captured command in a flow.
Change Governance is easier to search, brings access control for catalogs, packages, checks, and Assignments to parity with projects, pipelines, changelogs, and connections, with eleven new governance permissions, a Manage Access tool on every asset, and a Governance Lead template.
Change Automation makes
decorate-sqlavailable for Oracle and SQL Server only, lets you skip a changeset for a single update, fails Oracle changesets whose stored logic does not compile, extends--rollback-on-errorto four more platforms, handles largesqlFilescripts correctly, and strengthens the object-name policy checks.Liquibase Secure Server runs on your own PostgreSQL 17, including Amazon RDS, and the
liquibase-platformCLI gains--license,pull, andreset-password.Security introduces personal access tokens and removes secrets from more logs, containers, and command output.
Change Intelligence
Reports from cloud storage
Change Intelligence can now read operation reports that your pipelines write to cloud storage. Set reports-path to an az://<container>/<path> or s3:// location and Change Intelligence reads your reports from there, with no copy step in between. Teams that already keep HTML operation reports in a bucket next to their other pipeline artifacts get the same drill-down in the web interface without changing where the evidence lives.
Metrics that match the command line
Policy check counts and coverage metrics in the dashboard now match what checks run reports, so the number you see in a pipeline log and the number you see on the Policy Checks page are the same number. The run summary also lists each captured command with its own result, so when a CI flow runs several commands in sequence you can see which one failed rather than only that the flow did. Both changes make the dashboard a reliable place to answer "what happened" without going back to the raw log.
Change Governance
Easier to find and share policies
Search now matches more of what you type. Typing a check name with spaces, for example Object Name Must Match, finds ObjectNameMustMatch, so you do not need to remember the exact identifier of a check to locate it in a catalog. Owners can also manage access to catalogs, packages, checks, and Assignments with the Manage Access tool behind the gear icon on each one, which keeps the permission decision next to the asset it applies to instead of in a separate administration page.
Copying packages or checks between catalogs is more forgiving. When a copy would create a duplicate, Liquibase now skips it or renames it and tells you what it did, instead of failing the whole request, so sharing a proven package across teams no longer stalls on one name collision.
Finer-grained governance permissions
Access permissions for governance assets (catalogs, packages, checks, and Assignments) are now in parity with the RBAC options Liquibase Secure 6.0 introduced for projects, pipelines, changelogs, and connections. Asset owners can grant or revoke access for groups or individual users using any of eleven new governance asset permissions, through the Manage Access tool behind the gear icon on each asset, and a new Governance Lead template provides oversight of who can view, create, edit, and archive catalogs, packages, checks, and Assignments. Permissions are also enforced more precisely throughout the governance interface: you see, open, and pull only what you are allowed to. Governance leads get a template built for their role, and administrators can express "who may change the policy library" with the same groups, templates, and audit trail they already use for the rest of the workspace.
Important: When you upgrade from Liquibase Secure Server 6.0.0 to 6.0.2, the person who created each catalog, package, and Assignment becomes its owner, and every active member keeps view access to the catalogs and Assignments they could see before. Owners can instead revoke that inherited access from individual users on upgrade by setting LIQUIBASE_PLATFORM_GOVERNANCE_KEEP_PERMISSIONS_ON_MIGRATION=false in .env before running the upgrade. The setting is read once, during this upgrade only. To change access after the upgrade, use the gear icon on any asset and choose Manage Access.
Service principals now have a detail view in the web interface where an administrator can adjust project scope and overlay permissions without using the API, so scoping a pipeline credential to the projects it deploys is a routine administrative task rather than a scripted one.
Change Automation
The sections below describe what is new in Change Automation 6.0.2 as a delta from Liquibase Secure 6.0. Everything else works as described in the Liquibase Secure 6.0 release notes.
Deployment control
decorate-sql is available for Oracle and SQL Server only
decorate-sql is now a fully supported command, available for Oracle and SQL Server only, that turns raw SQL files into Liquibase-managed changelogs. It appears in --help and the standard command listings, and it accepts one or more folders in a single run, so a pipeline can decorate an entire release folder in one step instead of one file at a time. Teams that receive plain SQL from developers, vendors, or other tools can bring it under the governed path, with changesets, tracking, and policy checks, without hand-authoring changelog wrappers. decorate-sql supports Oracle and SQL Server only. It does not support other databases.
Skip a changeset without editing the changelog
When one changeset blocks a deployment, you can now skip it for a single update without touching the changelog. Use --ignore to name changesets or whole changelog files, or list them in a YAML file passed to --ignore-file, with an optional reason for each. Skipped changesets appear in the command output and in the HTML operation report, and they are not recorded as run, so they deploy normally the next time. The commercial Maven plugin has matching ignore and ignoreFile parameters. This keeps a release moving when a single change needs more work, while leaving a visible, reviewable record of what was held back and why.
More reliable deployments
Oracle compile failures surface immediately
A new --oracle-fail-options setting lets an Oracle changeset fail when its stored logic does not compile. Previously a package, procedure, or function with a compilation error could be created in an INVALID state and the changeset still reported success. With the option set, the failure is reported at the moment it happens, in the run that caused it, so a broken stored object is caught in the pipeline rather than discovered by the application that calls it.
Automatic rollback on error for more platforms
With --rollback-on-error, a failed changeset now runs its own rollback on MySQL, MariaDB, Snowflake, and Databricks, in addition to the platforms already supported. When a changeset fails part-way, Liquibase reverses what it applied instead of leaving the database in a half-changed state, so a failed pipeline stage can be re-run cleanly without manual repair.
Large sqlFile scripts handled correctly
Large sqlFile scripts now behave the same way as small ones. On Oracle, files of 1 MB or more that contain a q'[...]' quoted string no longer leave a package body INVALID. On SQL Server, files of 1 MB or more now split at every GO, exactly as smaller files do. Large migration scripts, which are often the ones that matter most, now deploy with the same statement-by-statement reliability as the rest of the changelog.
Important: Because large SQL Server scripts now split at every GO, a script that previously deployed as one batch can now fail on a statement that only worked inside a single batch. Review large SQL Server sqlFile scripts before you upgrade.
Preconditions and validation
Preconditions find objects without a schema name
The primaryKeyExists, indexExists, and foreignKeyConstraintExists preconditions now find existing objects when you leave out schemaName, resolving against the default schema the way the rest of Liquibase does. Changelogs written for one schema no longer need a schema name on every precondition to behave correctly, which removes a common source of "object not found" surprises when the same changelog runs against different environments.
validate --strict fails the build when it should
validate --strict=true now exits with a non-zero code when it finds errors. A pipeline stage that runs strict validation as a gate now actually stops on a bad attribute or an invalid include, instead of printing the error and letting the deployment continue.
Policy checks
Object-name checks cover more of your SQL
ObjectNameMustMatch and ObjectNameMustNotMatch now inspect more of your SQL. They cover columns added by addColumn, multi-clause ALTER TABLE statements, SQL Server ALTER TABLE ... WITH CHECK ADD, and statements wrapped in IF EXISTS blocks, and violation messages now name the offending object so the fix is obvious. Naming standards that previously applied only to the simplest statement shapes now apply to the SQL teams actually write.
Note: Because these checks now see more statements, changelogs that passed before can report violations after you upgrade. Review the results of the first run and adjust check targeting or the offending names as appropriate.
Cleaner PII check output
The PII checks no longer log false Unknown identifier warnings, so the checks report contains only findings that need attention and the noise that made real sensitive-data hits easy to miss is gone.
Changelog generation
Accurate defaults for binary, bit, and UUID columns
generate-changelog and diff-changelog now write more accurate default values for binary, bit, and UUID columns, so a generated changelog deploys the same defaults the source database actually has. Teams capturing an existing estate or detecting drift get a faithful changelog for these column types without correcting defaults by hand.
Note: Because the captured defaults have changed, take a new snapshot after you upgrade so that drift detection compares against the corrected values rather than reporting the correction as drift.
Database support
SQLite
On SQLite, addColumn now keeps the column default and NOT NULL constraint you specify, instead of dropping them when the column is added. SQLite changelogs behave consistently with the same changelog on other platforms.
MongoDB
MongoDB changelogs that use the collectionExists or documentExists preconditions now run correctly alongside the bundled Couchbase extension. Teams that manage both document stores from one Liquibase Secure installation no longer have to work around a conflict between the two extensions.
Cloud storage
Object names with spaces and special characters
Liquibase can now read Amazon S3 and Azure Blob Storage objects whose names contain spaces or special characters. Changelogs, SQL files, and other resources stored in a bucket no longer need to be renamed to a restricted character set before Liquibase can use them.
Liquibase Secure Server
Run the server on your own PostgreSQL
You can now run Liquibase Secure Server on your own PostgreSQL 17 database, including managed services such as Amazon RDS for PostgreSQL, instead of only the bundled database container. Organizations whose standards call for managed data services can point the server at a database they already back up, patch, and monitor, and keep the application tiers exactly as delivered.
Installing and updating with liquibase-platform
liquibase-platform install and update now take your license file with --license, so licensing is part of the install step rather than a separate configuration edit. A new pull command copies the server images into your own registry, which is the path for air-gapped environments and for organizations that only run images from an internal registry. liquibase-platform start now stops and names the port in use when another service already holds it, instead of failing with an opaque error.
Important: Docker Compose 2.20 or newer is now required for every liquibase-platform command. Check your Compose version before you upgrade.
Operating improvements
A new LIQUIBASE_PLATFORM_DB_POOL_MAX setting caps the number of database connections the server API opens, so you can size the server's footprint on a shared or managed PostgreSQL instance. liquibase-platform reset-password <email> prints a one-hour, single-use link so an administrator can recover access without SMTP. After you sign in, you land on the page you originally linked to, so a link to an operation or a policy shared in a ticket opens that page rather than the dashboard.
The audit log is now called the System Log and additionally records license management events, so license changes sit alongside permission changes in the same searchable, exportable record. Workspaces without a Business or Enterprise license now have two fixed groups, Administrators and Members. Adding a license turns Members into an ordinary editable group, and nobody's access changes when it does.
Security: tokens, credentials, and secrets
Personal access tokens
Per-user API keys are now personal access tokens. You can create, list, and revoke your own tokens through the API, and a token stops working as soon as its owner is deactivated, so offboarding a person also retires every credential they held. Personal tokens can no longer send operations or upload artifacts. That path belongs to service principal tokens, as described in the 6.0 release notes. Pipelines should use a service token, which keeps every ingested operation attributed to a machine identity created for that purpose.
Secrets kept out of more places
Liquibase Secure 6.0.2 removes secrets from several places they could previously appear. Database passwords and other secrets no longer reach the web container or show up in docker inspect output. liquibase-platform logs --bundle redacts your AI provider API key and other _KEY settings, and invitation and password-reset tokens no longer appear in logs. On the command line, Liquibase masks passwords in SQL logs and failed statements, your Snowflake auth token and private key passphrase, and your MongoDB password in status and history output. Support bundles, CI logs, and container metadata can be shared with less risk of leaking a credential.
Action required when you upgrade
Most of 6.0.2 needs nothing from you. These five changes do.
License retrieval through the API. Retrieving the signed license file through
/api/licenses/accessnow requires thelicensing:access:licensepermission. If a CLI fetches its license with a non-admin personal API key, switch it to a service principal API key.Personal API keys in CI. Personal API keys can no longer send operations or upload artifacts. Use a service token instead.
Custom Python policy checks. The built-in Python environment for custom policy checks no longer includes
urllib3and several unused standard library modules. Use--script-python-executable-pathwith your own environment if a custom check needs them.Large SQL Server sqlFile scripts. Large SQL Server
sqlFilescripts now split at everyGO. Review them before you upgrade.Governance asset ownership and access. On upgrade from Liquibase Secure Server 6.0.0, the creator of each catalog, package, and Assignment becomes its owner and active members keep the view access they had. To revoke that inherited access on upgrade, set
LIQUIBASE_PLATFORM_GOVERNANCE_KEEP_PERMISSIONS_ON_MIGRATION=falsein.envbefore you run the upgrade. Afterwards, adjust access with Manage Access on each asset.
Security vulnerability report
This release includes updates to internal platform components and third-party dependencies to address known security vulnerabilities and strengthen the overall platform security posture of Liquibase Secure. These updates help organizations maintain secure deployment environments, improve compliance readiness, and reduce operational risk associated with outdated software components.
CVE summary
Liquibase Secure also includes VEX (Vulnerability Exploitability eXchange) files with every release to communicate Liquibase's official assessment of reported CVEs. Refer to the VEX file included with the 6.0.2 release (files ending in .vex.json) for the complete list of vulnerability assessments and exploitability status. For more information about VEX files and how to interpret their status values, see the VEX documentation.
Full list of changes
GOV-234: Fixed an issue where saving the packages in an assignment could report an error even though the save succeeded, if the assignment was archived at nearly the same moment. This issue was present in Liquibase Secure 6.0.
GOV-241: Saving an assignment's composition now requires update permission on the assignment and view permission on every package you add, and packages and targets you can't see stay on the assignment when you save. If you try to remove one of them, the save is refused and nothing is changed.
GOV-248: You can now share a package on its own from the new Manage Access option in the package's gear menu, and you see a warning when a deny won't take effect because the person already has access through the catalog.
GOV-214: Copy to… now skips any check that is identical to one already in the destination package, and copies a check whose name is already taken there under the next free name. A message that stays open until you close it lists each skipped or renamed check and why.
GOV-217: The warning you see after importing a checks export with outdated files now stays on screen until you close it, and it shows a count of warnings with a See details link that lists each one.
GOV-253: Deleting a user through the API now succeeds when two users created catalogs or assignments with the same name, and anything a deleted user created now shows "Deactivated User" as its creator instead of no creator at all. Catalogs and packages created through the API with an API key before September 22 were saved with no creator, so after you upgrade they also show "Deactivated User" as their creator or last editor, even though nobody was deleted.
GOV-256: A Governance Lead can now manage owners and access on every catalog, package and assignment, including ones it doesn't own. It still can't manage access on projects, connections or changelogs.
INT-2406: A Cloud SQL socket factory JAR that you add to your classpath is now used instead of the copy of the connector bundled with the GCP extension, so connections that failed on Liquibase Secure 6.0.0 work again. A connection URL that names
socketFactory=com.google.cloud.sql.postgres.SocketFactory(or the MySQL socket factory) now needs your own connector JAR, as in 5.x, or you can set the password togcp-cloudsql-iamand setliquibase.cloudsql.instanceso Liquibase adds the socket factory itself. This issue was present in Liquibase Secure 6.0.0.SECURE-1035:
decorate-sqlon Oracle now keeps a PL/SQL block together when the first word afterBEGINis a name containing$or#that starts with a word such astrans(for exampletrans$cnt), instead of splitting it into several changesets that do not deploy. This issue was present in Liquibase Secure 6.0.SECURE-1057: Liquibase Secure now reads a backslash in a string literal as an ordinary character when you deploy a
sqlFileof 1 MB or more to PostgreSQL (whilestandard_conforming_stringsis on), DB2 or H2, so a literal such as'C:\'no longer merges the statements after it into one.SECURE-1062: The
ObjectNameMustMatchandObjectNameMustNotMatchpolicy checks now include the name of the offending table, column or other object in the violation message. Previously the message named only the object type, so two failing columns in one changeset printed identical messages.SECURE-1065: Passwords in a failed SQL statement (
IDENTIFIED BY,PASSWORD = '...'andSECRET = '...') are now masked as*****in theFailed SQLerror, the console output and the JSON log, so they no longer appear in plain text. The SQL sent to your database is unchanged.SECURE-1067: You can now skip changesets or whole changelog files for a single update with
--ignore, or list them, optionally with a reason, in a YAML file passed to--ignore-file, for example when one changeset blocks a deployment. The commercial Maven plugin has matchingignoreandignoreFileparameters. Skipped changesets are listed in the output and in the HTML report, and are not recorded as run.SECURE-1082: On MySQL and MariaDB, snapshots report the size of
LONGTEXTandLONGBLOBcolumns as2147483647again, sodiffand drift detection no longer show false changes against snapshots saved with 5.2.2.generate-changelogalso keepsUNSIGNEDon DECIMAL, FLOAT and DOUBLE columns and writes a size forVECTORcolumns, which 6.0.0 got wrong. Drift baselines saved with 6.0.0 show the affected columns as changed once, so save new baselines after upgrading. This issue was present in Liquibase Secure 6.0.0.SECURE-1085: A rollback that references another changeset, such as
--rollback changesetId:2 changesetAuthor:meor<rollback changeSetId="2" changeSetAuthor="me"/>, now works when one of the two changesets usesrunWith(sqlplus,sqlcmd,psqlorjcl) and the other runs over JDBC. Previously the native executor's settings carried over to the JDBC changeset, so its SQL was sent with the trailing semicolon andupdateorrollbackfailed, for example with ORA-00933 on Oracle. A formatted SQL changelog in a subdirectory whose rollback references a parent changelog'ssqlFileorloadDatachange withrelativeToChangelogFilealso passes validation now. These issues were present in Liquibase Secure 5.2.2 and 6.0.0.SECURE-1087:
ObjectNameMustMatch,ObjectNameMustNotMatchand the reserved-keyword checks now check the column added by anaddColumnchange (they used to check theafterColumnneighbour, or skip the change when no position was given), every clause of a multi-clauseALTER TABLE, the columns listed in aCREATE TABLE … (a, b) AS SELECT, named indexes declared next to unnamed ones, and objects created in a block that also holds other statements, such as aCREATE TABLEand anINSERTin one/orGOblock. Changelogs that passed before can therefore report violations. ACREATE TABLE … AS SELECTno longer makes the check fail with "No checks were executed". Column and index messages also name their table, for exampleObject type COLUMN name "id" in table "ACC_ORDERS" …andThe COLUMN named user in table orders is a Postgres reserved keyword. ….SECURE-1103:
ObjectNameMustMatchandObjectNameMustNotMatchnow also check the items after the first one when a singleADDlists several without repeatingADD, as SQL Server (ALTER TABLE t ADD a int, b int), Snowflake (ALTER TABLE t ADD COLUMN a int, b int) and Spark (ALTER TABLE t ADD COLUMNS a INT, b STRING) allow. Only the first item used to be checked. Columns count for the COLUMN object type, and named constraints and indexes in the list for INDEX, as they already did when written in their ownADD. Changelogs that passed before can therefore report violations. An item JSqlParser cannot read on its own, such asDEFAULT 0 WITH VALUESorPRIMARY KEY CLUSTERED, is still not checked. Also, SQL that cannot be parsed and nests more than ten parentheses is now reported by the checks that parse SQL as SQL they could not parse; it used to stop the check with "evaluated with error" and the run exited 0. This issue was present in Liquibase Secure 6.0.0.SECURE-1106:
ObjectNameMustMatchandObjectNameMustNotMatchnow check the columns and constraints added by a SQL ServerALTER TABLE … WITH CHECK|NOCHECK ADD …, the form SQL Server Management Studio generates. Such statements used to be skipped silently.SECURE-1115:
ObjectNameMustMatchandObjectNameMustNotMatchno longer report the keyword of a SnowflakeADD ROW ACCESS POLICYorADD SEARCH OPTIMIZATION, a DB2ADD PERIODorADD SECURITY POLICY, or a DatabricksADD PARTITIONclause as a column namedROW,SEARCH,PERIOD,SECURITYorPARTITION.SECURE-1116:
ObjectNameMustMatchandObjectNameMustNotMatchnow check aCREATE,ALTERorDROPstatement wrapped in SQL Server'sIF NOT EXISTS (…)/IF EXISTS (…)or in aBEGIN … ENDblock, the form SQL Server Management Studio generates with "Check for object existence" on. Such statements used to be skipped silently.SECURE-1162: The built-in Python environment for custom policy checks no longer includes the
ftplib,smtplib,poplib,imaplib,nntplib,telnetlib,cgitb,xmlrpc,cProfile,profile,pstats,pydoc,pydoc_data,idlelib,turtle,turtledemoandteststandard library modules. No Liquibase code used them, and a security review flagged them. A custom Python check that imports one of these modules now fails with aModuleNotFoundError.SECURE-1163: The built-in Python environment for custom policy checks no longer includes the
urllib3module. No Liquibase code used it, and a security review flagged its TLS 1.0 and 1.1 support. A custom Python check that importsurllib3now fails with aModuleNotFoundError.SECURE-851: On Oracle, a changeset that fails on its only statement no longer reports that manual intervention is required to restore database state. When
rollback-on-errorwas set, Liquibase ran that changeset's own<rollback>even though nothing had been committed, so the rollback tried to drop an object that was never created and Oracle rejected it. A changeset that commits one statement and then fails on a later one still runs its own rollback, which is the intended behavior. This issue was present in Liquibase Secure 6.0.0.SECURE-995:
sqlFilechanges with anendDelimiterwritten with an escape sequence, such as\nGOor\$\$, now split into separate statements when the file is 1 MB or larger, instead of failing because the whole file was sent as one statement. This issue was present in Liquibase Secure 6.0.0.SECURE-1125: [H2, MariaDB, Oracle] (SECURE-1125) generate-changelog and diff-changelog now keep the quotes of literal defaults on H2 uuid and binary(n) columns, MariaDB binary(n) columns and Oracle RAW and LONG RAW columns, so the generated changelog deploys and the copy gets the same default. Before, a uuid default such as '00000000-0000-0000-0000-000000000001' was written without quotes and H2 stored it as the number -1, and binary defaults made the CREATE TABLE fail. The same change applies to DB2 and Derby CHAR FOR BIT DATA and SQL Anywhere binary columns. Snapshots saved by earlier versions hold these defaults without their quotes, so a diff or drift report against such a snapshot shows them as changed until you take a new snapshot, and diff-changelog against it would write the old values back. Take a new snapshot after upgrading.
SECURE-1128: [MySQL, MariaDB] (SECURE-1128) generate-changelog and diff-changelog no longer fail with "Unknown boolean value" (LB-CHG-0032) on a bit(n) column whose literal default has more than one bit, such as b'1010', and diff-changelog no longer writes a changed default of that kind without a value; the default is written as defaultValueComputed="b'1010'" and deploys unchanged. MySQL 8 reports an expression default such as DEFAULT (b'1010') as 0x0a, which still fails. MariaDB bit columns are now generated with their size (BIT(4), BIT(1)) instead of BIT, which deployed as bit(1). diff-changelog now keeps BIT(n) as the type of a bit column with more than one bit in modifyDataType, addDefaultValue, addNotNullConstraint and the other changes that carry a column type; before, MySQL and MariaDB changed such a column to TINYINT(1) when those changes were deployed, and PostgreSQL rejected the type change. A bit(1) column is still written as boolean, so on MariaDB a NOT NULL, remarks or type change still turns it into TINYINT(1). A changed single-bit default (b'1', b'0') is now written with its value, as is a changed MySQL tinyint(1) or BOOLEAN default. Snapshots now store these defaults as b'1010' and MariaDB bit columns with their size, so a diff or drift report against a snapshot taken with an earlier version shows those columns as changed until you take a new snapshot. On HSQLDB generate-changelog now completes for these columns, but bit columns are still generated as BOOLEAN, so that output does not deploy.
SECURE-1135: [MySQL, SQL Server, Oracle, SQLite] (SECURE-1135) generate-changelog and diff-changelog no longer write MySQL 8 binary and varbinary defaults as 0X61626364, which MySQL and MariaDB reject; they are written as the database reports them, defaultValueComputed="0x61626364", and deploy. Any column default that a database reports as a single word starting with a digit now keeps its case, so SQL Server hex defaults (0x61626364, 0x01), Oracle numeric defaults such as 1e5 and SQLite hex defaults are written as reported instead of upper-cased; both forms deploy on those databases. A diff, drift report or diff-changelog against a snapshot taken with an earlier version does not report these defaults as changed. Where an older snapshot is the source of a change (a missing table, or a default that really changed), and in changelogs generated by earlier versions, the old 0X… text remains and still fails on MySQL: take a new snapshot or correct the value to 0x… by hand. An earlier version comparing a snapshot taken by this version reports these defaults as changed. On MySQL 5.7 binary defaults are still generated as unquoted raw bytes and do not deploy (SECURE-1144). MySQL 8 reports a binary default cut off at its first zero byte: an empty default, or one that starts with a zero byte, is written as 0x and does not deploy, and one such as 0x61006263 is written as 0x61, which now deploys with a different default where the update used to fail; check such defaults by hand (SECURE-1145).
SECURE-1146: Snapshot and generate-changelog no longer depend on the JVM's default locale when they upper-case a column's function default or recognise an Oracle identity default; on a Turkish-locale JVM,
current_timestampwas written asCURRENT_TİMESTAMP.SECURE-894:
decorate-sqlis now available for Oracle and SQL Server only and appears in--helpand the command listings. It converts raw SQL files into Liquibase-managed changelogs. The command existed in 6.0.0 but was hidden and intended for internal demonstration only.GOV-188: Every list endpoint (platform and Governance) now rejects an out-of-range
pageorper_pagewith a 400 that names the parameter: negative, fractional, non-numeric, larger than 9007199254740991, or a page/per_page pair whose offset would exceed that. Previously such values reached the database and the request failed with a generic 500.per_page=0is also a 400 now; it used to fall back silently to the default of 50.NTT-1579: Transferring ownership is no longer limited to the first 100 users. The picker shows a short alphabetical list and a search box that narrows it as you type.
NTT-1615: Creating an API key with a name longer than 32 characters now returns a validation error that names the limit, and the form enforces the same limit. Previously the request failed with a generic 500 error.
NTT-1629: The operations list and detail views now apply the type-specific view permissions for policy checks, drift, and database changes. A user whose template withholds one of those permissions no longer sees operations of that type, where previously the general operation view permission was enough.
NTT-1635: The Platform/DevOps Engineer template now includes the clone permissions for projects, connections, and changelogs, matching the create permissions it already held.
NTT-1638: The Application Developer, DBA, and Platform/DevOps Engineer templates now include the permissions to generate and view AI analysis. Customer Admin is unchanged.
SECURE-683: decorateSql now accepts one or more folders in a single run, so a pipeline can decorate an entire release folder in one step instead of one script at a time. Scripts are decorated in a deterministic order, and folders you do not name are left untouched.
SECURE-832: Liquibase now stops with a clear message when the Python environment passed to --script-python-executable-path was built against a different Python version than the runtime Liquibase embeds. Previously the environment's installed packages were left off the path with no warning, and custom policy checks failed with ModuleNotFoundError for packages that were installed.
SECURE-837: When a changeset fails on MySQL, MariaDB, Snowflake or Databricks and you run with
--rollback-on-error, the changeset's own rollback now runs and removes the objects it already created. These databases commit each DDL statement immediately, so a changeset that failed part-way previously left those objects behind. Oracle already behaved this way.SECURE-838: Policy checks no longer log an "Unknown identifier: ALL" warning for each changeset when a PII check uses the ALL identifier value. The checks always evaluated every identifier type correctly, so only the warning was wrong.
NTT-1718: When two checks share a name but differ in their settings or severity, the Checks Run count and the By Check tab on the Policy Checks details page now show each configuration as its own row with its own severity, instead of merging them into one. This issue was present in Liquibase Secure 6.0.0, and the fix needs the 6.0.1 CLI and server together.
NTT-1188: Fixed an issue where Change Intelligence showed fewer policy check violations than
checks runreported when you used--checks-scope=changelogand a changeset had more than one violation.NTT-1163: The Database Coverage and Changelog Coverage metrics on the Policy Checks dashboard now honor the checks scope, so a run scoped to
databaseno longer raises changelog coverage, and a run that executes zero checks no longer counts toward either coverage metric.SECURE-989: Fixed an issue where
checks run --helpandchecks show --helpnamed the legacyinsightssettings. The help text now namesliquibase.platform.apiUrlandliquibase.platform.apiKey.SECURE-923: Fixed an issue where
checks runskipped the Dynamo changetype attributes check without failing the run when acreateGlobalSecondaryIndexchangeset left outprovisionedThroughputor another optional block, so the check now evaluates these changesets normally. This issue was present in Liquibase Secure 6.0.0.SECURE-874:
decorate-sqlnow ignores spaces around the--db-typevalue, so--db-type="oracle "works the same as--db-type=oracleinstead of failing with an unsupported database type error. This issue was present in Liquibase Secure 6.0.SECURE-892: A new
--oracle-fail-optionssetting lets an Oracle changeset fail when its stored logic does not compile. The default isnone, which preserves the existing behaviour: the compiler output is shown and the deployment continues. Set it toerrors,warningsorallto have compiler output stop the job, matching what--sqlplus-fail-optionsalready offers for SQL*Plus. The Oracle compiler report on the console is also now labelled with its severity.SECURE-1055: Liquibase Secure now finds your existing
databasechangeloganddatabasechangeloglocktables on EDB Postgres Advanced Server databases created with--redwood-likewhen the schema name contains an underscore, so repeatedupdateandstatusruns no longer fail with "relation databasechangelog already exists". This issue was present in Liquibase Secure 6.0.0.INT-2405: Fixed an issue where commands such as
validate,update, andstatusfailed against Cloud Spanner (PostgreSQL dialect) through PGAdapter. This issue was present in Liquibase Secure 6.0.0.INT-2407:
tagnow records the tag when you run it on a Couchbase database that has no deployed changesets yet, so you can roll back to it later, andtag-existsnow returnstrueonly when the tag exists.INT-2410: A Google library JAR that you add to your classpath is now used instead of the copy bundled with the BigQuery extension, so the BigQuery extension no longer overrides the library versions you supply.
GOV-254: Copying packages to another catalog, or filling a catalog, now copies every selected package even when the destination already has one of that name: the copy lands under the next free name, such as Payments (1), instead of the whole request failing. A message that stays open until you close it lists each renamed package and its new name.
NTT-1755: The Utilization tab now shows a DB Target capacity of 1 as 1 instead of Unlimited, matching the Overview tab, so Compliance flags when you use more DB Targets than your license allows.
NTT-1642: The Liquibase Secure server web container no longer receives your database passwords, encryption key, authentication secret, AI key or SMTP password, so they no longer appear in
docker inspectoutput for that container, andliquibase-platform migrateandupdateno longer put your database password on thedocker runcommand line. This issue was present in Liquibase Secure 6.0.0.NTT-1805: The Drift Rate, Drift Detected, drift item totals and Database Coverage figures on the Drift Detection page and the dashboard now include
diffanddiff-changelogruns that fail because they breached your--drift-severitythreshold, so pipelines that gate on drift no longer see these figures undercount. This issue was present in Liquibase Secure 6.0.0.NTT-1831: The Liquibase Secure server audit log now records license management events, including license file imports, rejections, removals and re-verification, changes to your effective license status and licensed capabilities (recorded under the System actor when a license term or grace period ends on its own), and downloads and exports of license data, and you can filter the log to license events.
NTT-1797: liquibase-insights platform images ship VEX documents so customer scanners (Trivy, Grype) can distinguish assessed-not-exploitable CVEs from real ones, backed by our published exploitability analysis.
NTT-1385: After you sign in to Liquibase Secure server, you now land on the page you originally linked to instead of always landing on the dashboard.
NTT-1539:
insights install --domainnow adds an IP address as an IP entry in the generated certificate, so a client that trustscerts/server.crtcan connect to your server by that address without a hostname mismatch error.GOV-245: When you view an assignment that includes packages you don't have access to, you now see those packages by name under their catalog, and the page tells you how many changelogs, database connections and pipelines the assignment targets that you can't access.
GOV-246: You can't deactivate or delete a user, or delete a group, while they're the only owner of a catalog, package or assignment, and Transfer and deactivate now hands those items to the new owner too.
GOV-247: You can now manage who owns a catalog and who can access it from the new Manage Access option in the catalog's gear menu on the catalog list.
GOV-243: A service principal can now pull an assignment's checks settings file only when one of the assignment's targets is in one of the service principal's projects, and any other pull fails as if the assignment doesn't exist. An assignment needs at least one target before a service principal can pull it. If a CI pipeline pulls an assignment that doesn't target its projects, or has no targets, make sure its service principal has a project that contains one of the assignment's targets.
NTT-1207:
liquibase-platform installandupdatenow take your license file with--license, download and verify what they need, and pull the images without a separate credential. A newpullcommand copies the images into your own registry, andpull --filessaves a verified release thatinstall --filesinstalls offline from that registry. Every failure now prints an error code and what to do next.NTT-1815:
liquibase-platform start,installandupdatenow stop immediately and name the port in use when another service is already listening on the HTTP or HTTPS port, instead of reporting that Liquibase Platform is running.startandupdatealso recover on their own from a proxy container left broken by an earlier failed start, andstartexits with an error when the API can't be reached. To use different ports, setLIQUIBASE_PLATFORM_HTTP_PORTandLIQUIBASE_PLATFORM_HTTPS_PORTforstartandupdate, or pass--http-portand--https-porttoinstall.NTT-1852: Fixed the "Next steps" printed at the end of
liquibase-platform install, which sent you to the ingest endpoint and the personal API keys page. It now tells you to create your admin account and follow the setup guide for your version.NTT-1920: You can now cap the database connections the Liquibase Secure server API opens with the new
LIQUIBASE_PLATFORM_DB_POOL_MAXsetting (default 10), so the total stays below your database'smax_connections.NTT-1763: Fixed an issue where SAML metadata you upload for Entra SSO in the UI kept only one signing certificate and dropped the single-logout endpoint, which caused a false "no single-logout endpoint" warning in Verify configuration. This issue was present in Liquibase Secure 6.0.0, and providers you already registered keep the old values until you delete and re-register them.
NTT-1844: Fixed an issue where an operation sent with only a connection identifier or only a changelog identifier failed with a 403 error. These operations are now accepted and filed under the project that contains the identifier. An operation sent with no identifier, or with identifiers from different projects, now fails with an error that names the problem instead of pointing to your API key. This issue was present in Liquibase Secure 6.0.0.
NTT-1866: The
THIRD-PARTY-LICENSES.txtfile that ships with the Liquibase Secure server no longer includes dependencies under licenses Liquibase doesn't allow, such as the WTFPL.NTT-1416: You can now regain access to a self-hosted Liquibase Secure server without email by running
liquibase-platform reset-password <email>, which prints a one-hour, single-use link for choosing a new password.NTT-1892: Liquibase Secure server now refuses an invalid license file when you upload it and doesn't store it, so a wrong file can no longer get stuck in License Management, and importing the same file again now reports that it is already installed. This issue was present in Liquibase Secure 6.0.0.
NTT-1963: Fixed an issue where a user's API key kept working after that user's account was deactivated. The key is now refused with a 401 error. This issue was present in Liquibase Secure 6.0.0.
NTT-1958: Without a Business or Enterprise license, you can no longer configure groups, permission templates, overlays, or direct grants, and the API rejects those changes with a message naming the missing license capability. Promoting and demoting Administrators still works, and the Users page and License Management now state that all members can view all data in the workspace, including raw operation logs.
NTT-1957: If your workspace doesn't have a Business or Enterprise license, it now has two fixed groups, Administrators and Members. The first user to sign in is an Administrator, everyone who joins later is a Member who can start working right away, and Administrators can move people between the two groups.
NTT-1959: When you add a Business or Enterprise license, your Members group becomes an ordinary editable group and nobody's access changes; Administrators stays as it is. If the license later lapses, your groups, overlays and grants stay enforced as last configured, but you can't change them until you renew.
NTT-1929: You can now run Liquibase Secure server on your own PostgreSQL 17 database, including managed services such as Amazon RDS for PostgreSQL, by setting the
LIQUIBASE_PLATFORM_DB_*connection settings or passing--db-hostand the related flags toliquibase-platform install.install,updateandmigratethen apply migrations to that database. Docker Compose 2.20 or newer is now required for everyliquibase-platformcommand.NTT-2007: The
liquibase-platformCLI is smaller, which reduces the size of the installer download. A mistyped command now reportscommand <name> not found.NTT-1191:
liquibase-platform installnow fails with an error and a non-zero exit code when Liquibase Platform cannot be reached after installing, instead of reporting that it is installed and running.NTT-1783: Liquibase Secure server now keeps its database passwords, encryption key and authentication secret in files instead of container environment variables, so
docker inspectno longer shows them. New installs set this up for you, andupdatemoves an existing deployment over.NTT-1566: When you import more than one base license with identical terms, License Management now keeps the higher-tier license active instead of the lower-tier one.
NTT-1966: You can now create, list and revoke your own personal access tokens through the Liquibase Secure API. Each token expires after 30, 60 or 90 days (within the maximum your administrator sets), you can have up to 10 active tokens at a time, and the token value is shown only once when you create it.
NTT-1737: The Audit Log page in Liquibase Secure server is now called System Log, to make clear that it records events from administering the server, such as permission and account changes, and not activity on your databases.
NTT-1990: Fixed an issue where owning a project let you add, remove or transfer the owners of any changelog in it, even one you did not own. You now need to own the changelog yourself, or be a Customer Admin, to manage its owners.
NTT-1965: Personal API keys can no longer send operations or upload artifacts to Liquibase Secure, so use a service token for those. A personal access token otherwise works on every route its owner can use, except routes that manage tokens or your account, and a request made with the wrong type of credential, or with an expired, revoked or suspended token, now returns a distinct error code such as
credential_type_mismatchortoken_expired.SECURE-1064: License usage tracking messages and help text now refer to the usage tracking server and usage, instead of the license tracking collector and usage payloads.
NTT-2059: Liquibase Secure server no longer requires TimescaleDB: its bundled primary database now runs on standard PostgreSQL 17, so the server can also use managed PostgreSQL services such as Amazon RDS. When you upgrade an install that ran on the TimescaleDB image,
updateremoves the unused extension and moves the database to the standard PostgreSQL image. ATIMESCALEDB_IMAGEpin in.envis commented out and replaced withPOSTGRES_IMAGEfrom the same registry, so a mirrored install keeps pulling from its mirror.NTT-1976: When you upgrade to Liquibase Secure 6.0.1, every per-user API key becomes a personal access token that keeps its existing value and expires 90 days after the upgrade. A converted key is refused for operation ingest, so move any CI that ingests with a per-user key to a service token before you upgrade.
NTT-2050: After a self-signed install, the installer now tells you to replace
certs/server.crtandcerts/server.keyand restart when you want to use your own certificate, instead of suggestinginstall --force, which always failed on an existing install.NTT-2039:
liquibase-platform install,updateandmigratenow check that the external PostgreSQL database accepts the configured connection before changing anything, and name the reason when it does not.NTT-2054: Fixed an issue where the Administer menu in Liquibase Secure server stayed visible after you removed yourself from the Administrators group, so its entries opened to a no-access page until you reloaded.
NTT-2044:
liquibase-platform install,start,updateandstatusnow read the health of your Docker containers instead of probing the host over HTTPS, sostartno longer fails with error 0015 when your server uses a certificate issued to a hostname other thanlocalhost. If your Compose file predates the new container health checks, you see a warning instead of a failed setup.NTT-2017:
liquibase-platform stop,updateanduninstallnow stop the API container right away instead of waiting out a 10-second grace period and force-killing it, so it no longer showsExited (137).NTT-2038: The Liquibase Secure server bundle now ships its third-party license notices as
THIRD-PARTY-LICENSES.md, in the format our Legal team provides, instead ofTHIRD-PARTY-LICENSES.txt. If you script against the old.txtfile name, update it to the new one.NTT-2014: You can now store the Platform API key and the license endpoint URL, cache file and timeout settings in a secrets manager such as AWS Secrets Manager or HashiCorp Vault, and a Liquibase Secure node can still get its license from the license endpoint. If one of these settings cannot be resolved, the error now names the setting and shows the secrets manager failure instead of a generic license error.
GOV-207: Change Governance search now matches more of what you'd naturally type. Spacing out a check's camelCase short name finds the check, so
Object Name Must Matchnow returnsObjectNameMustMatch. A punctuation-separated value matches whether or not you put a space after the punctuation, so169, 170and169,170return the same results. The existing literal substring match is unchanged.GOV-208: Adding a target to an assignment now checks that you can see the project it belongs to. Saving a composition that adds a connection, changelog or pipeline from a project outside your visibility is rejected with a 400 naming the target, which matches what the picker already offers you. Removing a target is unaffected.
NTT-1106: Connection and changelog identifiers are now matched without regard to case, so
PSQL,psql, andpSqLall refer to the same one. You can no longer create a second identifier that differs only by case, and operations reported with a differently cased identifier now update the matching connection or changelog.GOV-249: You can now manage who owns an assignment and who can access it from the new Manage Access option in the assignment's gear menu on the assignment list.
NTT-1811: If you own an item such as a project, you can now manage who else has access to it, even when your template doesn't include grant permissions.
GOV-239: Governance search now returns only the packages and checks you have permission to view, and the match count includes only those results. Searching inside a catalog you can't see now shows the no-access page.
GOV-240: You now see, open, and archive only the governance assignments you have permission for, you need the create permission to add one, and you become the owner of any assignment you create. The unused duplicate-assignment API endpoint is removed.
GOV-242: Pulling a checks settings file now respects your permissions, so if you can't view some of an assignment's packages, the file leaves out their checks and Liquibase Secure warns you how many checks and packages are missing. Denying
everyoneview on an assignment also stops service principals from pulling it.GOV-244: When you upgrade, the person who created each catalog, package, and assignment becomes its owner, and every active member of a non-Pending group keeps view access to the catalogs and assignments they could see before. Owners can revoke that access from individual users. To skip keeping that view access, set LIQUIBASE_PLATFORM_GOVERNANCE_KEEP_PERMISSIONS_ON_MIGRATION=false in .env before running the upgrade; the choice is read once, on that upgrade, and cannot be changed afterwards.
NTT-1785: Fixed an issue where you could still open operations older than 24 hours through a direct link when Change Intelligence was unlicensed.
GOV-235, GOV-236: You can now control who can view, create, edit, and archive Change Governance catalogs, and who can import a checks file, using eleven new governance permissions and a new Governance Lead template. The person who creates or imports a catalog becomes its owner.
GOV-152: Assignment names must now be unique for each creator, and when you upgrade, existing duplicate assignments are renamed with a
-copyNsuffix (a name at the 255-character limit loses its last characters to make room for it).GOV-175, GOV-183: In the Change Governance assignment panel, you can now set a policy check's severity for a single assignment, and restore one package you marked for removal without discarding your other unsaved changes. Both count as unsaved edits, so the save confirmation lists them with the rest of the assignment's pending changes.
GOV-228: Select all on the Packages page, the Checks page and in search results now selects every item across all pages, not only the ones on screen. Assigning a catalog with more than 25 packages no longer leaves out the packages on later pages, so checks such as
ChangesetContextCheckare no longer missing from--assignment-idruns. Items selected across different pages are now all counted, and Assign and Copy include every one of them.GOV-237: You can now control who can view, edit, and archive Change Governance packages and checks, either through permission on a catalog or by sharing a single package. The person who creates a package becomes its owner.
GOV-238: Copying a package, copying or forking a check, and bulk enabling or disabling checks now require permission on every item involved, and a refused operation changes nothing. The person who copies a package becomes its owner.
NTT-1960: Workspaces without a Business or Enterprise license now give their Members group a Workspace Member template that you can view but not edit, and that is not offered on licensed workspaces.
NTT-1695: When Liquibase can't record license usage, it now prints a warning in the console instead of failing quietly. The command still succeeds, because usage tracking doesn't block a deployment by default. If you see the warning, check that
liquibase.license.utility.urlpoints at the base URL of your tracking service.NTT-1325: You can now set
reports-pathto an Azure Blob Storage location (az://<container>/<path>) and Change Intelligence reads the operation report from there, so it appears under View Report without a local copy. Liquibase authenticates with the standard Azure credential chain, such asaz loginor a managed identity.NTT-1145: Operations reported with a changelog identifier that only matches a deleted changelog are now left unattributed instead of being filed under the deleted changelog.
NTT-1177: The violation count shown for a policy checks operation now matches the count in the
checks runoutput, instead of including an extra entry for a changeset that a check does not apply to.NTT-566: An operation that finishes after Liquibase continues past a precondition set to warn (
onFail="WARN"oronError="WARN") now has a final status of warning in the Operations list instead of success. Other warnings in the log, such as database messages and theliquibase.propertiesnotice, do not change the status. This issue was present in Liquibase Secure 6.0.0.NTT-1934: The Outcome Breakdown in Operation Details now appears for
updateoperations that run with the default text log format. Before, the breakdown was missing unless you set--log-fileor--log-format=JSON. This issue was present in Liquibase Secure 6.0.0.NTT-1324: You can now set
reports-pathto ans3://location, and Liquibase reads the operation report from your S3 bucket so it appears under View Report.NTT-1912: The summary the Change Intelligence extension prints after a run now has a
Commands:section that lists each captured command with its own result, and the extension prints a one-line notice as each command finishes, so you can see which command in a CI flow failed.Final Statusstill reports the run as a whole. This issue was present in Liquibase Secure 6.0.0.NTT-1782: With Change Intelligence enabled, Liquibase Secure no longer prints license-service log lines to the console at startup, including one that quoted the beginning of your license key.
NTT-1217: The Properties table in the runtime summary on the Change Intelligence operation details page now lists only the properties you set, so internal properties such as
updateNullChecksumsno longer appear. This issue was present in Liquibase Secure 6.0.0.NTT-1949: Fixed an issue where Change Intelligence showed "The file: s3:/... doesn't exist" as a failed changeset's error, instead of the real error, when reports were written to an S3 or Azure path with liquibase.reports.open=true.
NTT-1950: Operations and HTML reports now follow the same credential rules, so a pipeline no longer sends an operation to Change Intelligence and then has its report rejected with a 403. A personal access token (the new name for a user API key) can't send either one, so use a service token. This issue was present in Liquibase Secure 6.0.0.
SECURE-946:
--include-objectsand--exclude-objectsnow treat a table's check constraints as part of the table. Including a table, withtable:<name>or a regex that matches its name, keeps its check constraints indiff,diff-changelog,generate-changelog, the drift report and the Maven and Ant equivalents, with the default diff types or any--diff-typeslist that includescheckconstraints; excluding a table drops them instead of writingaddCheckConstraintchanges for a table the changelog does not create. Other objects owned by a filtered object follow it the same way: the attributes of a PostgreSQL composite type, and on Snowflake and MongoDB the columns, keys, indexes and validators of a table, view or collection matched by a regex or by its own object type.checks run --checks-scope=database --verbosenow lists check constraints by their full name (catalog, schema, table, constraint), like columns, ordered by table; a custom check that reports an issue on a check constraint shows that full name as the object location; anddb-doclistsaddCheckConstraintanddropCheckConstraintchanges on the table's page when the change names the schema. Triggers do not follow a table filter yet.SECURE-1027: When Liquibase can't read a schema's metadata through the database's catalog views during a snapshot, the failure now reports
LB-DBX-0012with a suggestion on PostgreSQL, SQL Server, Db2 and Oracle, including when the failing load is for views or columns.SECURE-868:
decorate-sqlnow ignores a byte order mark (BOM) in the middle of your input, such as when you join two files that each start with one, instead of copying it into the next changeset and making that statement fail at deployment. This issue was present in Liquibase Secure 6.0.SECURE-963: The
primaryKeyExists,indexExistsandforeignKeyConstraintExistspreconditions now find existing objects when you leave outschemaNameon PostgreSQL, SQL Server, Db2, MySQL and Oracle, andprimaryKeyExistsno longer fails with aNullPointerExceptionwhen you give onlyprimaryKeyName. This issue was present in Liquibase Secure 6.0, and in Liquibase Secure 5.1-5.2 on Oracle.NTT-1800:
liquibase-platform logs --bundlenow redacts your AI provider API key and every other setting whose name ends in_KEYfrom the support bundle, and removes secret values and URL passwords from the bundled service logs. This issue was present in Liquibase Secure 6.0.NTT-1801:
liquibase-platform installno longer writes the unusedNEXT_PUBLIC_API_URLsetting into your generated.envfile, and the bundled.env.sampleno longer includes it. The web console readsRUNTIME_API_URL, which the bundled compose file sets fromLIQUIBASE_PLATFORM_WEB_URL.NTT-1829: License Management now has its own icon in the sidebar, so you can tell it apart from Service Principals.
NTT-1851: H2 no longer counts toward your licensed DB Targets or DB Types, never raises an unlicensed database type finding, and shows as H2 instead of PostgreSQL in Operation Details. Utilization figures for past reporting windows are recalculated under this rule.
NTT-1808: The Client credentials valid check in OIDC SSO verification now fails when your tenant ID does not exist or your client ID is not registered in the tenant, instead of reporting a pass. This issue was present in Liquibase Secure 6.0.0.
NTT-1774: Liquibase Secure server now requires the new
licensing:access:licensepermission to retrieve the signed license file through/api/licenses/access, so users without it can no longer download your license. Customer Admins and service principals keep access, but a CLI that fetches its license with a non-admin personal API key now gets a 403 error, so switch it to a service principal API key.NTT-1758: The utilization report now identifies each database target by the database type the CLI reports, so CockroachDB targets appear as
cockroachdbinstead ofpostgresqland are checked correctly against the database types your license allows. This issue was present in Liquibase Secure 6.0.0.NTT-1720: Metric text no longer overlaps in the 24-hour data window on the Database Changes and Drift Detection pages. This issue was present in Liquibase Secure 6.0.0.
NTT-1666: When you grant a user the
ops:view:connectionpermission on a project's Access tab, that user can now see the project's connections on the Database Connections page instead of a "You do not have access" message. This issue was present in Liquibase Secure 6.0.0.INT-2354: MongoDB changelogs that use the
collectionExistsordocumentExistsprecondition now run correctly alongside the bundled Couchbase extension, instead of failing with aClassCastException. This issue was present in Liquibase Secure 5.1-6.0.GOV-215: You can no longer save or enable a policy check while one of its required parameters is empty or contains only spaces, a value that
checks runtreats as unset. This issue was present in Liquibase Secure 6.0.0.SECURE-978: Fixed an issue where an Oracle
sqlFileof 1 MB or more containing aq'[...]'string with an apostrophe left a package body INVALID and skipped the statements after it, whileupdatereported success. This issue was present in Liquibase Secure 5.2.1-6.0.0.SECURE-991, SECURE-992: Fixed an issue where a SQL Server
sqlFileof 1 MB or more failed withIncorrect syntax near 'GO'when a procedure had anENDdirectly before anIForWHILE, or when a bracketed name such as[it's]contained an apostrophe or--. A SQL ServersqlFileof 1 MB or more now splits at everyGOthe same way a smaller file does, so a script that only deployed because it went out as a single batch can now fail. The bracketed-name issue was present in Liquibase Secure 5.2.1-6.0.0, and theENDissue in Liquibase Secure 6.0.0.NTT-1868: When you upload a consolidated license file, Liquibase Secure server now excludes only the individual licenses listed in it. Individual licenses it doesn't list keep counting alongside it, so capacity and SKUs are never counted twice.
INT-2332: When your Liquibase Secure license is invalid, Liquibase now reports the problem once instead of repeating it in the startup banner.
liquibase license statusnow describes a license read from a key, such asLIQUIBASE_LICENSE_KEY, as apre-6 license keyinstead of alocal license file, pre-6 format. This issue was present in Liquibase Secure 6.0.0.NTT-1821: At phone and tablet widths, the Liquibase Secure server web app now keeps the sidebar collapsed to an icon rail, the header no longer overlaps its icons, and wide tables scroll inside their own card instead of the whole page. This issue was present in Liquibase Secure 6.0.0.
NTT-703: Liquibase Secure server no longer accepts the undocumented
x-actual-valueheader on the connections endpoints, so API responses never include decrypted connection secrets.GOV-230: Fixed an issue where archived or deleted connections, changelogs, pipelines, and projects still appeared in a governance assignment and could not be removed. They now drop out of the assignment and its counts, and archived ones return when you restore them.
INT-2373: Liquibase now masks your Snowflake auth token and private key passphrase in the configuration log at
--log-level=FINE, so they no longer appear in clear text. This issue was present in Liquibase Secure 6.0.0.NTT-1828: Fixed an issue where Change Intelligence didn't capture or upload the HTML report for
update-count,update-to-tag,update-one-changeset,rollback-count,rollback-to-date, androllback-one-update, so these reports now appear with the operation.NTT-1862: Fixed an issue where the Drift detail page showed
public.in front of every object name for MongoDB and other databases that don't use schemas. Object names now appear without a schema prefix, and PostgreSQL databases still show their schema.SECURE-1012:
decorate-sql, andsqlFilechanges of 1 MB or more, no longer merge every statement after a string literal that ends in a backslash, such asESCAPE '\', into one statement on Oracle and SQL Server. This issue was present in Liquibase Secure 6.0.0.GOV-221: When you run
checks showorchecks runwith--assignment-idand the assignment has no checks, the command now fails with errorLB-CHK-0029saying the assignment exists in the Liquibase Platform but contains no checks. Before, you saw "check not found", nothing at all, or a passing run with no checks executed. A pipeline that points at an assignment with no checks yet now fails.NTT-1842: Fixed an issue where the dashboard briefly flashed on screen when you refreshed the page on a new install, before the registration or license import screen appeared. The correct screen now shows immediately.
NTT-1859: Fixed an issue where requesting an artifact under an operation it doesn't belong to returned the artifact instead of a 404 error. You now get a 404 unless the artifact belongs to the operation in the request.
NTT-1901:
checks runno longer prints a false "Potentially ignored key(s)" warning forchangeLogFilewhen you run database-scoped checks. With--strict=true, those checks also no longer fail with "The database target specified in the URL property cannot be accessed" because of that key.SECURE-1011:
decorate-sqlon SQL Server now treats aGOline that ends in a--comment, such asGO -- end of batch, as a batch separator, so the generated changesets no longer keep theGOand fail onupdate. This issue was present in Liquibase Secure 6.0.SECURE-1019: Fixed an issue where
updatefailed with ORA-00900 when an OraclesqlFileof 1 MB or larger had a comment on its own line, such as a/* ... */comment at the start of a line or any comment between a PL/SQL unit'sEND;and its/. In addition, on every database and at any file size, asqlFilestatement made only of comments (for example a comment after the last statement) is no longer sent to the database. It is skipped, and a warning is shown when the skipped comment contains text that looks like SQL. As a result, a small Oracle file that ends a PL/SQL unit with;and a trailing comment now completes successfully with the unit compiled INVALID, as the same file does without the comment, instead of failing with ORA-00900. Also, when a statement in an Oracle sqlFile of 1 MB or larger begins with a block comment that is never closed, update now fails at that statement with error LB-CHG-0048, which names the file and the statement's position, instead of the uninformative ORA-17104. The statements before it still run, as before. This issue was present in Liquibase Secure 6.0.SECURE-958: When
liquibase.license.endpointUrldoesn't supply a license and Liquibase falls back to the license configured on your node, every command now says so on the console, with the reason the endpoint gave.liquibase license statusshows the same reason on a newLicense endpoint:line, and names a license on the node that doesn't verify as a key or a file instead of as the endpoint. Embedded runs (Spring, Maven, the Java API) keep logging it at WARNING, now in the new wording.SECURE-994: Fixed an issue where
updatefailed on a SQL ServersqlFileof 1 MB or larger that contained a nested block comment, or a comment betweenBEGINandTRAN. This issue was present in Liquibase Secure 6.0.GOV-232: The Assignments dropdown now shows who created each assignment, so you can tell apart assignments that have the same name.
INT-2374: Liquibase no longer exposes your MongoDB password in the connection string that
statusandhistoryprint, or in connection error messages. This issue was present in Liquibase Secure 5.0.2 through 6.0.0.NTT-1893: Invitation and password-reset tokens no longer appear in container logs or in the support bundle you create with
liquibase-platform logs --bundle. This issue was present in Liquibase Secure 6.0.0.SECURE-1010: On SQL Server, a
sqlFileof 1 MB or more with noendDelimiternow splits atGOlines the same way smaller files do, soupdateno longer fails withIncorrect syntax near 'GO'. This issue was present in Liquibase Secure 6.0.0.SECURE-813:
validate --strict=truenow exits with a non-zero code and shows the coded error and suggestion on STDERR when strict validation finds errors (for example, an emptydbmsattribute), instead of reporting success. This issue was present in Liquibase Secure 6.0.SECURE-996: Liquibase now reports the error right away when a failed statement contains one very long line, instead of appearing frozen for minutes. This issue was present in Liquibase Secure 6.0.0.
SECURE-1043: Fixed an issue where the
liquibase-commercialMaven artifact declaredmockito,byte-buddyandobjenesisas dependencies, so they were pulled into your project and you had to exclude them by hand.NTT-1627: Archived connections no longer appear in a project's relations or in the pipeline pickers. An archived connection can no longer be added to a project.
NTT-2073:
liquibase-platform updatenow shows you every pending upgrade notice before it changes anything and asks you to typeyesto continue (pass--non-interactiveto accept automatically).installandupdatealso refuse a--tagthat is newer than your CLI, so download the matching CLI first.SECURE-1185:
decorate-sqlnow writes JSON and YAML changelogs that Liquibase can read when a changeset has two or more rollback statements, soupdateno longer fails withLB-CHG-0009. This issue was present in Liquibase Secure 6.0.SECURE-1137: A uuid column default written as a literal in defaultValue, such as 00000000-0000-0000-0000-000000000001 (also the 32 digits without hyphens), is now quoted when the table is created or the column added, so it deploys on PostgreSQL, MariaDB, MySQL, H2 and HSQLDB. Before, it was written without quotes and failed at deploy, or on H2 was stored as -1 and failed on the first insert. Changelogs generated from a MariaDB 10.7+ uuid column with a literal default now deploy. Other text in a uuid defaultValue, such as an expression like (UUID()), is written as before. On Oracle the column is RAW(16), so use the 32-digit form without hyphens. update-sql output and SQL-format changelogs now show the quoted literal. On MySQL a 32-digit default used to be stored as the number 1 and is now stored as written.
SECURE-1149: Running a diff no longer causes later snapshots and diffs in the same process to leave out object types. Previously, a diff against a snapshot that covered fewer object types, such as a MySQL snapshot, removed those types for the rest of the process. This affected flow files that run a diff and then a snapshot, and long-running integrations such as the Maven plugin, Spring Boot and the Java API.
SECURE-1168: On SQLite, addColumn now creates the column with its default and its NOT NULL constraint, and existing rows take the default. Before, both were silently dropped for every type. As a result, some addColumn changesets that used to pass now fail the same way createTable fails with the same column: a function default without parentheses such as datetime('now') (write it as (datetime('now'))), a function SQLite does not have such as NOW(), with or without parentheses (use CURRENT_TIMESTAMP), a sequence default, NOT NULL without a default (or with the default NULL) on a table that has rows, and UNIQUE with a default on a table with two or more rows. A uuid literal default fails until SECURE-1137 is in the same release. With runInTransaction="false", a failure in the row copy leaves the table empty with the rows in _temporary, and a failure in the CREATE leaves only _temporary; both need manual cleanup before the changeset can run again (a sequence default fails before anything runs). A foreign key default now fills existing rows even when the parent table has no such key. A non-integer primary key with a default now deploys on a table with one row. Columns added by earlier versions keep no default; their changesets do not run again. A function or apostrophe default added this way is rewritten by the next change that rebuilds the table (SECURE-1174).
NTT-1977: When you run
checks runwith a personal access token, Liquibase Secure 6.0.2 prints one INFO line saying results were not sent to Change Intelligence and exits with code 0, instead of failing, because personal access tokens cannot send operation data. Use a service token in CI so your runs are recorded. Earlier versions of the extension treat this refusal as an error.NTT-2055: Creating a workspace no longer creates a "Default" key, and the
POST /api/workspacesresponse no longer includesdefault_api_key.SECURE-1174: On SQLite, a change that rebuilds the table (addColumn, dropColumn, addDefaultValue, addAutoIncrement, mergeColumns) now keeps the existing columns' defaults as SQLite stored them. Before, a function default such as CURRENT_TIMESTAMP, or an expression default on a text column, became plain text, an apostrophe doubled again at every rebuild, an expression default on another column lost the parentheses SQLite needs and made the rebuild fail, and a REAL or NUMERIC default was rounded. generate-changelog and diff-changelog now write these defaults the same way, mostly as defaultValueComputed. A diff or diff-changelog against a SQLite snapshot file taken with an earlier version reports these columns as changed on an unchanged database: retake the snapshot. A diff between two SQLite databases now reports a function or expression default against the same text as a string, the string 'NULL' against no default, and a decimal on a text column, or a number on a BOOLEAN, DATE, DATETIME, JSON, UUID or STRING column, against the same number written as a string, even though SQLite stores the same value (INTEGER, REAL and NUMERIC columns still compare equal); it no longer reports two spellings of the same string, or DEFAULT NULL against no default. A string default on a date or time column, such as DATETIME DEFAULT 'CURRENT_TIMESTAMP', now stays that string through a rebuild; it used to become the function. checks run with a ConstraintMustExist DEFAULT rule now treats a column declared DEFAULT NULL as having no default.
NTT-2004: A request that cannot get a database connection within the pool timeout now fails with a 503
Database connection pool timed outerror instead of hanging the API until you restart it. You can set the wait withLIQUIBASE_PLATFORM_CONN_TIMEOUT_MILLIS, which defaults to 5000 ms.GOV-218: The catalog and package pickers in Governance (Copy Check, Save As, bulk Copy to…, and the Packages and Checks pages) now show the first 100 items followed by a Load more option, so catalogs and packages past the first 100 are no longer missing from the lists.
GOV-220:
checks show --checknamenow keeps the capitalization you typed when it reports a check it can't find, so you see'SqlRevokeWarn'instead of'sqlrevokewarn'. When you list several check names without a checks settings file,checks shownow shows each listed check once instead of repeating the first match, and reports an unknown name listed next to a valid one as not found instead of ignoring it.GOV-276: You can now reuse the name of an archived check when you save a copy of a check into the same package.
GOV-277: Check names in a package are now unique regardless of letter case, matching how Liquibase Secure looks up checks by name. Copying a built-in check into a package where another check already uses its name is now refused.
NTT-1978: Liquibase Secure server now calls API keys service tokens and personal access tokens in the console, in permission names and in new audit entries, and the
/api-keyspage redirects to the personal access tokens page. Your existing groups, overlays and grants keep the same effective permissions.SECURE-1047: On Oracle, the
dbcl-historyfilters--executed-sqland--extensionsnow return the matching history rows instead of failing with ORA-00932 or ORA-22848 (or ORA-01704 for a value over 4000 bytes). They match like the other filters: the whole value, ignoring case. The connecting user needs EXECUTE onDBMS_LOB, which Oracle grants to PUBLIC by default. Other databases are unchanged.SECURE-1114: On PostgreSQL, EDB and CockroachDB, generate-changelog and diff-changelog now keep a
bpcharcolumn without a length asbpchar. Before, they wrote it asCHAR, which createscharacter(1), so values longer than one character no longer fit, and on PostgreSQL amodifyDataTypeto such a column (from diff-changelog or written by hand) cut existing values to one character. A changelog that you wrote by hand withtype="bpchar"and no length (alsobpchar ARRAYor with a collation) now creates an unboundedbpcharcolumn too, as PostgreSQL does, where it used to createcharacter(1); on Redshift it now creates Redshift'sBPCHAR(CHAR(256)) instead ofCHAR(1). Changesets that already ran are not re-run, so a database updated before this version keepscharacter(1), anddiffagainst one updated after reports the type.char,characterandbpchar(n)are unchanged, and so are databases outside the PostgreSQL family.SECURE-1036: Fixed an issue where deploying a
sqlFileof 1 MB or more to PostgreSQL failed withLB-DBX-0004(Unterminated block comment) when a;followed the inner*/of a nested block comment. Liquibase Secure now keeps a nested block comment in one piece, the way PostgreSQL reads it.INT-2416: Liquibase Secure now wraps the
TAGcolumn of theDATABASECHANGELOGtable in double quotes on Teradata, so creating and querying the table no longer fails on Teradata versions whereTAGis a reserved word. Existing tables keep working, because quoted and unquotedTAGresolve to the same column.GOV-280: You can now open the gear menu from the assignment, package and catalog pages themselves, with the same options as on the list cards, such as Manage Access, so you no longer have to go back to the list to manage them.
GOV-282: Clicking anywhere on an assignment, package or catalog card now opens it.
GOV-283: The Access page's back link now returns to the assignment, package or catalog page it was opened from, and Manage Access opens in a new tab on cmd/ctrl-click from every gear menu.
NTT-2097: Fixed an issue where running
updateagain after it failed at the migration step overwrote.env.bakwith the version that failed. The error then wrongly said your services were running that version, and restoring.env.bakno longer returned you to your previous one.SECURE-1026: The
indexExistsprecondition now honoursschemaNamewhentableNameisn't given. Before, it always looked in the connection's default schema, so an index that exists only in the named schema was reported missing, and an index in the default schema, or a schema that doesn't exist, made the precondition pass.catalogNamewithouttableNamenow scopes the lookup the same way where the database uses it: on MySQL and MariaDB it names the database, and on Oracle and DB2 it names the schema (when both are given, Oracle and DB2 search thecatalogNameone). So a catalog that doesn't exist now fails the precondition; SQL Server and PostgreSQL with Liquibase Secure ignorecatalogName, as before. AtableNamewith spaces around it is now trimmed. WhentableNameisn't given, the failure message now names the catalog and schema from the changelog, for exampleIndex IX_A in schema APP does not exist. Unchanged: SQLite, and DB2 for z/OS, whereschemaNameis still not used for this lookup. Teradata and Cassandra were not tested.SECURE-1034: Liquibase no longer fails with "Illegal character in path" (or "Malformed escape pair") when an S3 location holds an object whose name contains a space, a
%not followed by two hex digits, or a few other special characters. This affectedincludeAll, changelogs, flow files and checks settings files with such names,decorate-sqlfolders,init projectfrom S3,checks runandgenerate-changelog --overwrite-output-file. Azure Blob object names get the same fix.decorate-sqlwith its root changelog on S3 now writes the real file name in the include for a script whose name holds#,?or a literal%20, so the aggregator deploys. Paths of S3 and Azure Blob objects in messages and logs are now URI-encoded, as local paths already are: a name holding#,?or%followed by two hex digits shows as%23,%3For%25xxthere, while the object is still read and written under its real name.SECURE-1094: Passwords in SQL are now masked as
*****in the executed-SQL lines of the--log-level=FINElog (and--sql-log-level=INFO), thechangelogPropertieslog field, MongoDBcreateUserpasswords and the stack traces Liquibase writes to the log, so they no longer appear in plain text. The SQL sent to your database, the update report andDATABASECHANGELOGHISTORYkeep the real text.NTT-677: You no longer need to pass
--dirto everyliquibase-platformcommand: afterinstall, commands such asstatus,logsandstopfind your deployment by checking--dir, then theLIQUIBASE_PLATFORM_DIRenvironment variable, then the current directory, then the directoryinstallrecorded.SECURE-1279: The license information file shipped with Liquibase Secure has a new, easier-to-read format.
GOV-289: When you run
checks showorchecks runwith--assignment-idand your API key can't view any of the assignment's packages, the error now says the checks were withheld because of permissions, instead of saying the assignment contains no checks.SECURE-897: Fixed an issue where formatted SQL changesets failed with a
ClassCastExceptionwhen the Liquibase Percona extension (liquibase-percona) was installed, even for changesets that did not setusePerconaExtension.NTT-1479, NTT-1488, NTT-1538: Long pipeline names, API key names, and usernames no longer break their layout in the web interface. Stat card summary text wraps on smaller screens, and the login form's validation message no longer carries the internal field name.
NTT-901: The OpenAPI specification that Liquibase Secure server serves at
/api/openapi.jsonnow loads in strict OpenAPI validators, so tools that validate it or generate clients from it no longer reject it, and the API reference at/api/docsno longer shows/api/apipaths.GOV-224: You can now remove the file you selected in the Import dialog, so you can pick a different one without closing the dialog.
GOV-163: When you import a checks-settings file in the legacy format 1.0 (created by Liquibase 4.21 and earlier), the import error now names the unsupported format and gives you the command to upgrade the file, instead of a generic invalid-file message. This issue was present in Liquibase Secure 6.0.0.
NTT-863: When
diffbreaches your--drift-severitythreshold, Change Intelligence now records the operation as a failure that matches the CLI exit code, instead of showing it as a success. This issue was present in Liquibase Secure 6.0.0.NTT-1492: Change Intelligence no longer transmits the local OS username, the absolute working directory path, or unsanitized connection strings embedded in error stack traces.
NTT-1682: The console and its transactional emails now identify themselves as Liquibase Secure Server. Change Intelligence remains the name of the licensed module within it.
NTT-2013: Fixed an issue where the request log (
GET /api/audit/http) recorded status 200 and no user for every request. Each entry now shows the status code that was actually sent and the user who made the request.NTT-2061: Liquibase Secure server now ships patched versions of follow-redirects, handlebars, compression, shell-quote, sharp, engine.io, joi and Next.js, which clears the Critical and High CVEs reported against them in the server images. This issue was present in Liquibase Secure 6.0.0.
NTT-2067: The bundled databases now run PostgreSQL 17, the only supported major. During
update, existing data is copied to new volumes, so plan a maintenance window.updateshows the data size and asks before it starts; pass--non-interactivein pipelines.apiandwebare down while the copy runs, and the host needs enough free disk for a second copy of the data. The old volumes are kept until you remove them. If you run your own PostgreSQL image,updatekeeps it, but it has to be a 17 build: pointPOSTGRES_IMAGEat it and runupdateagain. If you use an external database, upgrade it to 17 through your provider before you update.NTT-2087: Removes the undici, multer, fast-uri, body-parser, cookie-parser, qs, ip-address, fast-copy, fast-xml-parser, @babel/core, DOMPurify, nodemailer and better-auth CVEs from the platform images, and publishes VEX statements for 13 CVEs.
NTT-2195: Removes the distrusted eMudhra root certificates from the Secure Server migrate container.
SECURE-787: An assignment id listed as a source inside a checks packages file is not supported yet. Liquibase now stops with LB-CHK-0031 and asks you to use the assignment on its own with
--assignment-id, instead of failing with a not-found error for that entry.checks run,checks showandchecks describewith a package selection (--checks-packages, the defaults file or the environment) and no checks settings file now stop with LB-CHK-0032 and create nothing. Before, they created a default checks settings file and the example packages and ignored the selection, or, when headless, failed with a not-found error; with--forceand a missing--checks-settings-file, they created that file. A package selection used with a checks settings file that is not a packages file is still ignored, now with a warning.SECURE-797: Liquibase Secure now starts and runs normally when you install the community Neo4j extension 5.0.3 or later, and uses its own
diffin place of the extension's. This issue was present in Liquibase Secure 5.2.0-6.0.1.SECURE-1008: With a Secure licence on PostgreSQL, tables whose names differ only by case (such as a quoted "MixedT" next to mixedt) no longer share primary keys, indexes and foreign keys in snapshot, diff and generate-changelog, and existence preconditions answer for the table they name instead of its twin, as in 5.2.2. Behaviour change from 6.0.1: primaryKeyExists and indexExists with a tableName, and foreignKeyConstraintExists with a foreignKeyTableName, again match the table name exactly as Liquibase resolves it under the changeset's objectQuotingStrategy, the same way tableExists does and as they did in 5.2.2. tableName="Orders" for a table created as orders, or tableName="LONE_UPPER" for a table created as "LONE_UPPER", passed in 6.0.1 (and, for foreignKeyConstraintExists, in 6.0.0) and now fails. With the default onFail="HALT" such a changeset stops the update, and a precondition wrapped in now lets its changes run. To keep these changesets working, give the stored name in a changeset with objectQuotingStrategy="QUOTE_ALL_OBJECTS". A snapshot saved by 6.0.0 or 6.0.1 of a schema with such tables recorded the merged objects; take a new one before diffing against it. Known limitation: generate-changelog of such tables still produces a changelog that cannot be deployed, as in 5.2.2.
SECURE-1076: DB2 LUW: snapshot, diff and generate-changelog report the same column sizes as Liquibase Secure 5.2.2 again. 6.0.0 reported storage lengths in bytes, so generate-changelog wrote DDL that DB2 rejects, such as
DECFLOAT(8), and diff reported false type changes against snapshots taken with 5.x. generate-changelog on DB2 LUW also now keeps CODEUNITS32 string units (when the target is DB2 LUW),TIMESTAMP(0),LONG VARGRAPHIC, identity START WITH and INCREMENT BY values, the INCLUDE columns of unique indexes, and expression-based index keys. Lower-case table and column names are quoted in XML, YAML, JSON and formatted SQL changelogs. The statistical views DB2 creates for expression-based indexes are no longer generated as views, and drop-all no longer fails on them. DB2 for i (liquibase-commercial-db2iextension): snapshot, diff and generate-changelog no longer run the DB2 LUW catalog queries that 6.0.0 also ran on DB2 for i. Behavior changes to be aware of on DB2 LUW: Snapshots saved with 6.0.0 show column type differences, such asINTEGER(4)againstINTEGER(10), when compared with a database snapshotted by this version, even if nothing changed. Take new baseline snapshots after upgrading. Snapshots saved with 5.x compare cleanly. diff no longer reports a difference between a CODEUNITS32 column and an OCTETS column of the same declared size. 6.0.0 reported one only as a side effect of its byte-length sizes; 5.x did not report it either. Columns of user-defined (distinct) types are generated as in 5.x: the type name with its representation size, for example"APP"."MONEY"(9, 2), which DB2 rejects. 6.0.0 generated the representation type instead (DECIMAL(19, 4)in that example), which deployed but changed the column's type. Edit such columns in the generated changelog before deploying. Identity columns defined GENERATED ALWAYS are still generated as GENERATED BY DEFAULT, so that generated data changesets, which insert explicit identity values, can deploy. Identity START WITH in generated changelogs is the identity's next value, so a table copied with its data keeps numbering after the copied rows instead of colliding with them. Aunique="true"createIndex withincluded="true"columns now creates a unique index on the key columns only. 6.0.0 added the included columns to the key, so the index allowed rows that are now duplicates; existing data with duplicate keys fails with SQL0603N.