2020-01-23 by Alex Tercete
Flyway 6.2.0 is out! This release contains new features and improvements over Flyway 6.1.0.
The highlights of the 6.2.0 release include:
-colorCLI option to allow overriding the default colorization
flyway.validateMigrationNamingoption to fail validation if scripts that don’t match the naming pattern are found in one of the configured locations
We’ve also written a guide for adding support to your database.
You can find a detailed list of issues fixed in the release notes.
We’ve added the
flyway.validateMigrationNaming configuration option to enforce the naming pattern for scripts in the configured locations. When set to
true, validation will fail if any such scripts are found. If left as
false (the default and current behavior), such scripts are ignored.
This can be useful to identify scripts with naming errors such as
V1_My_description.sql (single instead of double underscore used as separator) or
v1__My_description.sql (lowercase instead of uppercase “v” used as prefix).
Previously, if at least one schema in
flyway.schemas already existed, none would be created. Flyway will now create all non-existing schemas.
We’ve added the
-color CLI option to allow overriding the colorization strategy. Set it to
never to disable it,
always to enforce it and
auto (the default and current behavior) to colorize when appropriate (e.g. when attached to a console).
We’ve published a guide for people who want to see their database supported by Flyway.
You can download Flyway 6.2.0 now! We recommend you upgrade if you are affected by any of the issues logged in the release notes.
Now it’s your turn! Spread the word, follow @flywaydb on Twitter and subscribe to our newsletter below to be the first one to be notified about updates.