Bot releases are visible (Hide)
Published by mariochampion about 2 years ago
liquibase flow
command and flow files are still available under the Liquibase Labs license.
flow
is here: https://docs.liquibase.com/flow
update-one-changeset
and update-one-changeset-sql
serving as complements to rollback-one-changeset
and roll-back-one-changeset-sql
AS <dataType>
clause for H2 since version 2.0 by @marcus-nl in https://github.com/liquibase/liquibase/pull/3047
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.15.0...v4.16.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Contribute code
Make doc updates
Help by asking and answering questions
Set up a chat with the Product team
Thanks to everyone who helps make the Liquibase community strong!
Published by mariochampion about 2 years ago
liquibase flow
commandliquibase flow
and new flow-file (DAT-10419) by in https://github.com/liquibase/liquibase/pull/2946
liquibase flow
command and the Flow File on which it operates allow the user to place multiple commands within a single file so they can all run sequentially with a single command into the CLI. This is currently a Liquibase Labs restricted capability, so please contact [email protected] to request a license key. Learn more at http://docs.liquibase.com/flow.No security updates needed in this release.
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.14.0...v4.15.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Contribute code
Make doc updates
Help by asking and answering questions
Set up a chat with the Product team
Thanks to everyone who helps make the Liquibase community strong!
Published by github-actions[bot] about 2 years ago
Split liquibase-core and liquibase-commercial jar files by @nvoxland in https://github.com/liquibase/liquibase/pull/3050
Added liquibase.changelogParseMode setting by @nvoxland in https://github.com/liquibase/liquibase/pull/3057
No security updates needed in this release.
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.13.0...v4.14.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Contribute code
Make doc updates
Help by asking and answering questions
Set up a chat with the Product team
Thanks to everyone who helps make the Liquibase community strong!
Published by nvoxland over 2 years ago
PRO DAT-10083 - Added PSQL native executor feature by @abrackx
runWith
command to pull in PSQL changesets which require highly specialized SQL that often cannot easily be deployed over JDBC. For more information, see the documentation here.No security updates needed in this release.
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.12.0...v4.13.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Contribute code
Make doc updates
Help by asking and answering questions
Set up a chat with the Product team
Thanks to everyone who helps make the Liquibase community strong!
Published by nvoxland over 2 years ago
Support for Snowflake database has been moved from the external extension liquibase-snowflake into the main Liquibase artifact. If you are using the snowflake extension, remove it from your lib
directory or however you are including it in your project. If you are using the Docker image, the snowflake
docker label will no longer be updated so you need to update your reference to either latest
or the version tag you prefer. For CLI users, the Snowflake driver also ships out of the box and so you should remove that from the lib
directory as well https://github.com/liquibase/liquibase/pull/2841
The Quality Checks commands have moved from limited availability in Liquibase Open Source to complete unlimited access only in Liquibase Pro. If you were using the Liquibase Open Source version, which was limited to five checks, you can test out the unlimited version with a free Liquibase Pro trial.
* make all QCs work only for Pro users (Pro PR 496) (DAT-10098)
${...}
string that doesn't correspond to a set changelog property. The default continues to be "preserve" which leaves it as-is. But other possible values are ERROR or EMPTY which will either stop execution with an error or replace it with an empty string. By @dwieland in https://github.com/liquibase/liquibase/pull/2656
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-4.12.xsd
type XSDs references, you can now also use http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd
instead. By using "latest", Liquibase will use the bundled XSD for it's version. The uploaded "latest" XSD will always be the most recent Liquibase release, so note how they can be different and locally cached IDE versions may be different yet. By @nvoxland in https://github.com/liquibase/liquibase/pull/2886
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.11.0...v4.12.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Contribute code
Make doc updates
Help by asking and answering questions
Set up a chat with the Product team
Thanks to everyone who helps make the Liquibase community strong!
Published by nvoxland over 2 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues.
Starting with 4.11, we moved the global libraries we ship with the CLI from the lib
directory to a new internal
directory structure. The lib
directory is still included in the classpath as the place users can add whatever additional global drivers/libraries they need.
The liquibase --version
output has been enhanced to also include the 3rd party libraries being used and their versions.
Impacts:
lib
and internal/lib
. You should manually delete any files in lib
which you did not add yourself. Liquibase will continue to work even with the duplicate libraries, but you may not be running the latest version of ones we ship, since the lib
files take priority over what is in internal/lib
. New installs are not impacted by this.lib
you will need to update it to reflect the new internal/lib
locationFor security reasons, we have also changed what is logged by the CLI to only log liquibase
channel messages by default, rather than all log channels. If you are relying on logging from non-Liquibase libraries, you can add channels with the new --log-channels
flag, including --log-channels=all
to restore the old functionality.
lib
and into a new internal/lib
directory by @nvoxland in https://github.com/liquibase/liquibase/pull/2850
--monitor-performance
argument for the CLI (and only the CLI) which enables profiling of the Liquibase run. The generated profiling information can help us understand and fix performance issues easier. https://github.com/liquibase/liquibase/pull/2599
(0)::real
by @nvoxland in https://github.com/liquibase/liquibase/pull/2836
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.10.0...v4.11.0
Published by mariochampion over 2 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues.
Upgraded mssql driver to 10.2.0 by @nvoxland in https://github.com/liquibase/liquibase/pull/2790
End User Impact: The driver changed the encryption default from "false" to "true" between 8.x and 10.x. If you have a self-signed certificate in your database, you must do one of the following: add encrypt=false
; add trustServerCertificate=true
; or add the server certificate to the java trusted certificate list. For production systems, Liquibase recommends against using self-signed certificates without adding the server certificate to the Java keystore. For more information on installing the trusted certificate, see https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/manage-certificates?view=sql-server-ver15
Upgraded postgresql from 42.3.2 to 42.3.4 to address CVE-2022-26520 by @dependabot in https://github.com/liquibase/liquibase/pull/2769
checks.run
and checks.show
goals [DAT-9033] [DAT-9034]Full Changelog: https://github.com/liquibase/liquibase/compare/v4.9.1...v4.10.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Contribute code
Make doc updates
Help by asking and answering questions
Set up a chat with the Product team
Thanks to everyone who helps make the Liquibase community strong!
Published by nvoxland over 2 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues.
[PR#2666] [nvoxland] Liquibase 4.9.1 release is a patch release that fixes the MANIFEST.MF
location in the liquibase.jar
file for tools that require the MANIFEST.MF
file to be the first entry in the jar archive.
If the MANIFEST.MF
file is not the first entry, java.util.jar.JarInputStream#getManifest()
reading the MANIFEST.MF
file will not return the manifest information appropriately. The PR fixes issue #2648.
[Issue#2672] Addresses the remaining OSGi-related packaging problems to fully restore Liquibase support in OSGi environments.
[PR#2651] Fixed the issue with a malicious software alert for the Liquibase macOS Installer preventing from proceeding with the installation. [DAT-9524]
[PR#2643] Fixed an issue in snapshot on PostgreSQL where non-integer datatypes that used a default value with a sequence would not be handled correctly [DAT-8670]
[PR#2691] Fixed invalid JSON in the example-changelog.json file [DAT-9893]
Fixes security issue in which sqlcmd outputs userid and password when using loglevel=INFO [DAT-9571]
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.9.0...v4.9.1
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Published by nvoxland over 2 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues.
Liquibase 4.9.0 introduces the following functionality:
secureParsing
parameter to prevent the entity resolver from scanning the network for missing XSDs. If you reference an XSD other than one from Liquibase and have never stored them in your classpath
, Liquibase will no longer automatically download and use the XSD from the internet for security reasons. The default value for secureParsing
is true
, but you can set it to false
in any of the Liquibase configuration locations. For more information, see XSD support.uniqueConstraintExists
precondition to check for the existence of unique constraints before running the update. You can check the constraint by constraint name or columns:<preConditions>
<uniqueConstraintExists constraintName="uq_constraint_name" tableName="test_table"/>
</preConditions>
<preConditions>
<uniqueConstraintExists tableName="test_table" columnNames="first_name, last_name"/>
</preConditions>
<listener>
<listener-class>liquibase.integration.servlet.LiquibaseJakartaServletListener</listener-class>
</listener>
The PR fixes issue #2298.
validate
goal to maven-liquibase-plugin
to provide access to the existing Liquibase validate
command and be available not only in CLI, but also in Mavensqlcmd
on an instance with multiple databases [DAT-9513]--schemas
argument to the snapshot
command to be able to compare a multi-schema database to its snapshot [DAT-9433]generate-changelog
command so that you can check if the splitStatements
attribute works for your environment when generating formatted SQL changelogs [DAT-9327]StripComments
attribute for the SQLUserDefinedPatternCheck
quality check to choose the code that the SQLUserDefinedPatternCheck
searches, including the option for the commented code. The StripComments
attribute strips comments from SQL before searching for the string. The default value is N
(no). [DAT-9098]--should-snapshot-data
CLI parameter to be preserved when the --data-output-directory
property is not specified in the commandreferenceSnapshot
parameter instead of referenceDatabase
for the potential null valueexample-changelog.sql
file that comes with the Liquibase installation package [DAT-9325]FormattedSqlChangeLogParser
to be reusable for extensionsonlyUpdate
attribute is false
in the loadUpdateData
Change Type for HSQLSMALLSERIAL
, SERIAL
, and BIGSERIAL
for versions earlier than 21.2GENERATED BY DEFAULT AS IDENTITY
for version 21.2 or laterendDelimiter
attribute not being respected during the Liquibase update. The fix for endDelimiter
does not break the handling of trailing comments in SQL statements. [LB-2186]SET DEFAULT
[DAT-8779]loadData
Change TypeFull Changelog: https://github.com/liquibase/liquibase/compare/v4.8.0...v4.9.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Published by github-actions[bot] over 2 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues.
Liquibase 4.8.0 introduces the following functionality:
init hub
subcommand that connects your local Liquibase activity to Liquibase Hub and sets up the Liquibase environment to use Liquibase Hub. [DAT-8769]Note: For more information, see init hub and Getting Started with Liquibase Hub.
sqlcmd
utility support to process complex SQL for MSSQL Server. Liquibase provides the liquibase.sqlcmd.conf
file to pass arguments to your executor when running Liquibase Pro. [DAT-7447]Note: For more information, see Using the SQLCMD integration and runWith attribute with Liquibase Pro and MSSQL Server.
liquibase.secureParsing=false
. [PR#2384] [LB-2218]Note: For more information about the ways to set the parameter, see Command Parameters.
postgresql
(from 42.2.12
to 42.3.2
) and h2
(from 2.0.206
to 2.1.210
) drivers that Liquibase includes in the installation package. If you use those drivers and upgrade an existing Liquibase installation, remove the earlier versions of drivers from the LIQUIBASE_HOME/lib
directory.SimpleObjectConstructor
interface for DB2 on z/OS [DAT-8580]init project
subcommand [DAT-9041]init start-h2
when the H2 database driver is specified, but there is no connection detected [DAT-8992]enableCheckConstraint
, disableCheckConstraint
, dropPackage
, dropPackageBody
Change Types [DAT-9017]example-changelog.sql
file [LB-2220]customChange
node with no class
attribute [LB-1144]rollback-sql <tag>
operation [LB-2198]close
method for the ClassLoaderResourceAccessor
class [LB-2205]renameSequence
Change Type generating an uppercase SQL instead of lowercase and causing failures with case-sensitive databases [LB-1763]generate-changelog
and diff
commands to show and generate a proper SQL with autoincrement for PostgreSQL [DAT-8779]<sql>
tags [LB-562]UniqueConstraintSnapshotGenerator
class to add a table name to the Oracle database query so that the cache key can contain it, and the unique constraint can be read from cache [LB-2206]update-sql
command against a new database [LB-2208]MANIFEST.MF
file in the liquibase-core-4.7.0.jar
file. The PR fixes PR#2361.sp_rename
function to be lowercase when using MSSQL Servercomputed=true
columns with no type set in the createTable
Change Type. The PR fixes PR#2283. [LB-2215]ordered
clause is specified in the createSequence
or alterSequence
Change Type. The PR fixes PR#2528.dbms
filters. The PR fixes PR#2231. [LB-2217]Full Changelog: https://github.com/liquibase/liquibase/compare/v4.7.1...v4.8.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Published by github-actions[bot] over 2 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues
In version 4.7.0, users that have "edb" in connection URLs but are not using EnterpriseDB experienced errors that caused Liquibase to misinterpret the database dialect. This patch release resolves this issue along with several others.
RollbackRequired
. The check detects when a changeset does not have a rollback. [DAT-8871]TableColumnLimit
check to work with formatted SQL changelogs [DAT-8531]--auto-update
quality check parameter, which allows automatic backup and updating of the liquibase.check-settings.conf
file when new quality checks are available. [DAT-8752]
--auto-update=[on|off]
liquibase.properties
file: liquibase.command.checks.show.autoUpdate: [on|off]
LIQUIBASE_COMMAND_CHECKS_SHOW_AUTO_UPDATE=[ON|OFF]
Note: You can use the property not only with the show
command but any other quality checks command.
liquibase-maven-plugin
logging configuration as deprecated [LB-2183]listLocks
output message. The PR fixes PR#2029. [LB-2126]FormattedSqlChangeParser
[DAT-4793]init project
command if you miss a supported argument in any command [DAT-8641]EnterpriseDBDatabase
detection less broad. The implementation of EnterpriseDBDatabase
picked up database with "edb" in the URL instead of an actual EDB URL. The PR fixes PR#2363. [LB-2214]OBJECT_TYPES=TABLE, COLUMN, SEQUENCE
specified in the same ObjectNameMustMatch
rule to find all matches [DAT-8716]runWith=changeLogProperty
attribute not working in a formatted SQL changelog [DAT-4793]cacheSize
attribute in the createSequence
and alterSequence
Change Types for MariaDB. The PR fixes PR#2147. [LB-2191]tag-exists
command old syntax in Liquibase 4.4 and later (liquibase tagExists myTag
) to correctly convert the pattern into new versions. The PR fixes PR#2109. [LB-2192]columnDataType
attribute for the generated setColumnRemarks
changesets to fix an error in MySQL [LB-2199]Full Changelog: https://github.com/liquibase/liquibase/compare/v4.7.0...v4.7.1
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by github-actions[bot] almost 3 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues
Liquibase 4.7.0 introduces the init
command with the project
and start-h2
subcommands.
init project
subcommand helps to set configuration files for using Liquibase or, if you already use Liquibase, create new project files with minimal input. [DAT-8640]init start-h2
subcommand helps to start the included in-memory H2 database. The subcommand needs to be run in a new terminal window. [DAT-8945]Note: For more information and examples of using init
project, see init project.
Additionally, we have updated the Liquibase Getting Started tutorials, sample changelog files, and the example H2 database in the installation package. From now on, you can use sample SQL, XML, JSON, and YAML changelog files with the corresponding changesets and the latest version of H2. [LB-2177] [LB-2174]
Note: Check Liquibase Getting Started to see more details.
rollback-one-update
command [DAT-7590]jdbc:edb
URL for Liquibase to recognize EnterpriseDB [LB-2185]sys.synonyms
objects for the generate-changelog
and diff-changelog
commands in Liquibase and SQL Server. The PR fixes PR#2044. [LB-2175]liquibase.sqlplus.conf
file and put the file in the examples/sql
folder [DAT-7618]
loadData
performance [LB-2173]generateChangeLog
wrong dependency order: the addPrimaryKey
Change Type appeared before its base table in PostgreSQL [DAT-8256]loadData
Change Type to recognize CSV files when loading data with the path that contains a dot character ('.') [LB-2178]addNotNullConstraint
Change Type causing the "Data too long" error message. The PR fixes PR#1054. [LB-2187]relativeToChangelogFile
attribute for loadData
, createProcedure
, and createView
Change Types [LB-2179]COLUMN_SIZE
for the PostgreSQL NUMERIC[]
datatypeFull Changelog: https://github.com/liquibase/liquibase/compare/v4.6.2...v4.7.0
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by github-actions[bot] almost 3 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues
Liquibase 4.6.2 introduces the multiple objects quality check that allows you to define and check the naming pattern for multiple types of objects rather than one type of object. For example, you do not want to have a dash in the table, column, and sequence names. With the multiple objects check, you can specify a pattern to check for dashes and choose tables, columns, and sequences as the objects to check. In version 4.6.2, the check is available for:
Note: For more information, see Multiple Objects Quality Check [DAT-8444]
Liquibase 4.6.2 includes the liquibase.sql.logLevel
configuration option to control the level at which SQL is logged. The default value is FINE
.
You can run the --sql-log-level
parameter with the --log-level <level>
parameter in the CLI:
liquibase --sql-log-level <FINE|INFO|SEVERE|WARNING|OFF> --log-level=<FINE|INFO|SEVERE|WARNING|OFF> --log-file=log.txt update --changelog-file=<changelog>
You can also set the parameter as follows:
liquibase.sql.logLevel: <FINE|INFO|SEVERE|WARNING|OFF>
in your liquibase.properties
fileLIQUIBASE_SQL_LOG_LEVEL=<FINE|INFO|SEVERE|WARNING|OFF>
as an environment variable [PR#1520] [nvoxland]liquibase_libs
directoryWhen you run Liquibase in the CLI, the executables generate a classpath with the .jar
files from the LIQUIBASE_HOME
and LIQUIBASE_HOME/lib
directories. Liquibase 4.6.2 adds the ability to load an additional directory of liquibase_libs
in the current working directory to the classpath. With the liquibase_libs
directory located in the /lib
directory, projects can have separate extensions, drivers, and versions specific to a project [PR#2015] [mcred]
validate
command in automationFrom now on, the exit code for the validate
command running in automation shows 1
when there is an error. The PR fixes PR#1006. [PR#2185] [nvoxland] [christf]
DDL_LOCK_TIMEOUT
parameter for Oracle without SQL Plus and define the connection timeout. You can configure DDL_LOCK_TIMEOUT
as follows:
liquibase.ddlLockTimeout: <value>
in your liquibase.properties
file--ddl-lock-timeout=<value>
as a CLI global parameterLIQUIBASE_DDL_LOCK_TIMEOUT=<int>
as an environment variable [DAT-7649]SqlUserDefinedPatternCheck
quality check copy [DAT-8492]MSSQLDatabase
specific error evaluation when creating DATABASECHANGELOGLOCK tableNOT NULL
constraint with an initial default value in the addColumn
Change Typeremarks
attribute in a primary key column tag for MariaDBaddColumn
Change Type in SQLitegenerate-changelog
command to generate the NUMERIC[]
data type for PostgreSQL correctlyalterSequence
Change Type to be compatible with the Oracle, PostgreSQL, MariaDB, and MSSQL databases--verbose
flag used in the unexpected-changesets
command. The PR fixes PR#1987.YAMLChangelogParser
and changeLogId
in a Map. The PR fixes PR#1988.GENERATED ALWAYS AS
clause while creating a table for PostgreSQLLOCKGRANTED
column to include time zone information in the DATABASECHANGELOGLOCK tableDB2Database
implementations. The PR fixes PR#2058.ColumnConfig.java
documentationrelativeToChangelog=true
parameter for Spring Bootsnapshot
command failing against CockroachDB with the Liquibase Pro license key applied [DAT-8253]addPrimaryKey
Change Type generated by the generate-changelog
command for PostgreSQL [DAT-8256]LIQUIBASE_COMMAND_CHECKS_CONFIGURE_CHECKS_SETTINGS_FILE
, LIQUIBASE_COMMAND_CHECKS_RUN_CHECKS_SETTINGS_FILE
, and LIQUIBASE_COMMAND_CHECKS_SHOW_CHECKS_SETTINGS_FILE
to be detected when running the quality checks commands [DAT-8546]strict
parameter. The default value is false
. You can set the strict
parameter as follows:
liquibase.strict=false|true
in your liquibase.properties file--strict=false|true
as a CLI parameterLIQUIBASE_STRICT=false|true
as an environment variable [DAT-8547]Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by suryaaki2 almost 3 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues.
Published by suryaaki2 almost 3 years ago
Please report any issues to https://github.com/liquibase/liquibase/issues
Starting with version 4.6.0, the Windows and Mac/Linux Liquibase installers and the .tar.gz and .zip installation files include the most common JDBC drivers in the installation package:
To use the available drivers, see the Adding and Updating Liquibase Drivers documentation. Also, check the page for the cases when you need different drivers. [PR#2031] [DAT-7438]
Note: Since Liquibase 4.6.0 provides driver jar files, the size of the installation package is bigger than the size of the installation package in earlier versions.
GRANT WITH ADMIN OPTION
statement is detected [DAT-7955]GRANT WITH GRANT OPTION
statement is detected [DAT-7995]liquibase.checks-settings.conf
file is unencoded in version 4.6.0 and later versions for easier inspection that allows you to resolve a merge conflict in source control. Liquibase backs up encoded files in the working directory, and you can still use previous versions by specifying the --checks-settings-file
parameter in the CLI, as an environment variable, or as a property in the liquibase.properties file. [DAT-8473]If you use Liquibase Hub, check the Liquibase Hub DevOps metrics documentation to learn more about DevOps metrics that provide the data to optimize your DevOps performance.
errorOnMissingOrEmpty
attribute to true
for the includeAll
attribute in the XML changelog file. The PR fixes PR#1960.createTable
Change Type. The PR fixes PR#1597
constraintName
attribute in the dropNotNullConstraint
attribute. Updated the addNotNullConstraint
rollback logic to pass the constraint name to the generated dropNotNullConstraint
change. The PR fixes PR#1492 and PR#1942.liquibase.util
packagedatetime
type to datetime2
for the timestamp
type on SQL Server.liquibase.fileEncoding
setting, which you can set as --file-encoding=ASCII
in the CLI, liquibase.fileEncoding: ASCII
in the liquibase.properties file, and LIQUIBASE_FILE_ENCODING=ASCII
as an environment variable. The PR fixes PR#1445.strict
attribute is set to true
[DAT-6946]snapshot
command using for CockroachDB with Liquibase Pro license key [DAT-8253]ChangesetCommentCheck
check to handle a lack of comments in the tagDatabase
Change Type [DAT-8313]liquibase.checks-settings.conf
files [DAT-8328]checks customize
and checks copy
commands to handle directories with spaces [DAT-8389]schemas
and includeSchema
attributes for the generateChangeLog
command in Liquibase 4.4 and later versions [DAT-8133]insert
Change Type with the valueSequenceNext
and valueSequenceCurrent
attributes to use the schema specified on a statement level of a changeset. The PR fixes PR#1304.LicenseService
interface cannot be loaded because of the missing jaxb
dependenciesUniqueConstraintSnapshotGenerator
class switching to a bulk query after four unique constraints. The PR fixes PR#1996.--changeset
line. The PR fixes PR#1919.dropAll
command failing in the PostgreSQL database when the Liquibase-Cassandra extension is in the liquibase/lib
directory. The PR fixes PR#47.liquibaseSchemaName
and liquibaseCatalogName
configuration settings. The PR fixes PR#2000.dropPrimaryKey
attribute for PostgreSQL. The PR fixes PR#1933.sqlFile
Change Type to handle the encoding
attribute. The PR fixes PR#1760.Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by suryaaki2 about 3 years ago
Liquibase 4.5.0 is now available at Liquibase.org.
Here is a closer look at what we improved in the latest release.
Please report any issues to https://github.com/liquibase/liquibase/issues.
Liquibase 4.5.0 includes support for Liquibase Quality Checks, which allow you to run checks against changelogs and SQL scripts by flagging conditions and configurations you need.
There is a new family of commands to use to run quality checks:
liquibase checks show
to list the available quality checksliquibase checks run
to run the available quality checksenable
, disable
, customize
, copy
, reset
, and delete options, and
liquibase checks --help` to learn moreThe following is a list of changes related to Liquibase Quality Checks:
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at: https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at: https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by nvoxland about 3 years ago
Liquibase 4.4.3 is now available at Liquibase.org.
Here is a closer look at what we improved in the latest release.
This release includes many community-contributed pull requests, Liquibase Open Source and Liquibase Pro bug fixes, and enhancements to Liquibase Hub performance and pipelines.
In Liquibase 4.4.3, there are improvements to the FileSystemAlreadyExistsException
output message. The original FileSystemNotFoundException
warning was changed to be an info
message that does not include logs of stack traces. If you are still seeing stack traces, please contact us. #1885 dertin
Additionally, we fixed bugs in SQL files: #1798
sqlFile
and relativeToChangelogFile
attributes fail when using the logicalFilePath
attribute #1277 darkcamper
relativeToChangelogFile=true
and databaseChangeLog
has logicalFilePath != PhisicalFilePath
#1353 kezhevatov
dropAll
command on DB2 for iSeries #1412 wardvijf
logicalFilePath
attribute not being serialized #1471 tms-91
SqlParser
bug related to parsing UTF-8 valid symbols #1513 matteoturra
InsertOrUpdateGeneratorHsql.java
#1563 devorgpl
customChange
Change Type has no name
attribute #1592 danielthegray
isNumericBoolean
now checks the Firebird3Database
instance type and returns Boolean for Firebird 3. #1875 koushikd02
ClassCastException
in a standard lock service: java.time.LocalDateTime
cannot be cast to java.util.Date
#1878 jocmer-evooq and haidiiii
CUBE
to the list of Liquibase reserved columns for the schema migration to work. CUBE
is a reserved word as of MySQL 8.0.1 #1515 jasonwjones
CLOB
data into PostgreSQL. Instead of loading the CLOB
file name, PostgreSQL loads the content of the CLOB
file. #1791 jidma
RawSqlStatement
to UpdateStatement
#1602 biryukovpavel
ChangeLogHistoryServiceFactory.java
#1361 Olard
DATICAL_SPERRORLOG
table when using the runWith=sqlplus
attribute and executing operations as a user with only SELECT
, UPDATE
and INSERT
permissions [DAT-7410]liquibase/liquibase-github-action-example
repository [DAT-6679]dropAll
report to work with a registered changelog with no extra arguments and send the information to Liquibase Hub [DAT-7554]tablespaceName
parameter to liquibaseTablespaceName
[DAT-7676]Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at: https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at: https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by suryaaki2 about 3 years ago
Liquibase 4.4.2 is now available here and through our website.
Here is a closer look at what we improved in the latest release.
This release includes community-contributed pull requests, Liquibase Open Source and Liquibase Pro bug fixes, and enhancements to the dropAll
command and SQL*Plus.
UniqueConstraintSnapshotGenerator
does not handle more than four unique constraints. The diff
command reports a difference in unique constraints caused by the PostgreSQL database snapshot having fewer unique constraints than the snapshot from another database compared. Also, the issue can cause unreliable diffs and changelog generation for all non-MySQL databases. The fix will be available in the next release. #1996
NullPointerException
to ChangeLogParseException
for the output when there is a typo in a changeSet
node #1593 danielthegray
support
method to DatabaseConnection
#1784 alexandru-slobodcicov
serial
and bigserial
if liquibase.convertDataTypes=false
#1883 szandany
ConfigurationValueProvider
performance #1952 stuartwdouglas pmancaux
defaultValue
attribute #1963 ZwoCa
-D
arguments in the CLI #1943 Gama11
updateTestingRollback
command #1939 chornota
unexpectedChangeSets
#1972 szandany
generateChangeLog
command.runwith:sqlplus
being stopped unless Liquibase includes a quit statement.dropAll
command with optional hubConnectionId
and hubProjectId
attributes. For more information, check our dropAll command documentation.connectionjdbcurl
when there is no project or connection ID with the dropAll
command.dropAll
command.Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at: https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at: https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by suryaaki2 over 3 years ago
Liquibase 4.4.1 is now available here and through our website.
Here’s a closer look at what's included in the latest release.
This release introduces SQL*Plus fixes for Liquibase Pro users, addresses some Liquibase Hub integration issues, along with some other bugs listed below.
Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at: https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at: https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger:
Published by suryaaki2 over 3 years ago
Liquibase 4.4.0 is now available here through Liquibase.org.
Here’s a closer look at what's included in the latest release.
While there are significant changes in important Configuration and Command APIs, and a new CLI library, this release should be 100% backwards compatible. Please report any issues to https://github.com/liquibase/liquibase/issues
--help
contentLearn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at: https://learn.liquibase.com/.
Please check out and contribute to the continually improving docs, now at: https://docs.liquibase.com/.
Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to make it stronger: