v4.3.0
This release includes many community-contributed pull requests, bug fixes, and an enhancement to Liquibase Hub integration represented by two new capabilities — optional auto-registration to Liquibase Hub from the CLI and Liquibase Hub report links presented in CLI.
Also, MariaDB is now fully certified for Liquibase Pro users.
Bug fixes
- Fixed NullPointerException when an output writer is null #1625
- Fixed filename + Id + author to be treated as unique in ValidatingVisitor.findChangeSet method #1622
- Fixed EntityResolver to check the classpath even if the standard ResourceAccessor does not include it #1621
- Fixed HistoryCommandTest to run on systems having a non-US default locale #1078
- Added quotes around ${JAVA_PATH} in Liquibase shell script to avoid spaces in path issues #1062
- Fixed the issue with automatic dropping of default values on MS SQL #1003
- Allowed --changeset to have a space after -- in formatted sql files
Improvements
- Updated the snakeyaml driver (that is packaged with Liquibase installer files) to address the CVE-2017-18640 vulnerability #1608
- Modified SetColumnRemarks support for MySQL #942
- Implemented boolean data type support for DB2 LUW #966
- Added deprecated LogFactory.getInstance() to make it easier for users who use the third party extension code to upgrade to 4.x #1642 and #1641
- Included the existing dropPrimaryKey.dropIndex attribute in XSD #1629
- Implemented auto-registration and operation report capabilities for Liquibase Hub
- Certified MariaDB and Liquibase Pro functionality. Determined and documented MariaDB Oracle-compatible PL/SQL stored logic objects along with minimum GRANTs to leverage Liquibase Pro with MariaDB 10.4. See Liquibase Pro and MariaDB GRANT Best Practices.