org.flywaydb:flyway-database-databricks

Changes

• connections now report their application name as "Redgate_Flyway" rather than "Flyway by Redgate" on every database that supports it

• Databricks connections now identify Flyway to Databricks as "Redgate_Flyway" via the UserAgentEntry connection property

• drift results are published to Flyway Pipelines for any drift check when publishResult is enabled, not only for checks against a Flyway Pipelines snapshot

• Flyway now sets the pgjdbc assumeMinServerVersion property to 9.1 on PostgreSQL connections

• testConnection.environmentName names the environment supplied on standard input, so provisioners act on the environment being tested rather than standing up a second one, and progress and error messages name it rather than default

Database compatibility

• added Snowflake support for the snapshot history feature

Bug fixes

• connections to PostgreSQL and CockroachDB now report application_name as "Flyway by Redgate" rather than the pgjdbc default

• the docker provisioner built container connection URLs against localhost, which could resolve to an address the container was not published on, so clients failed to connect to a container Flyway had reported as ready

New features

• Flyway MCP adds a new Test Migrate tool that runs pending migration scripts against your configured shadow database.

• Flyway MCP now also supports 3-sided diff by creating a checkpoint of the schema model before updating, so it can be compared against the development database.

Changes

• remove unnecessary executable files from JRE package

Database compatibility

• Issue 4282 Fix older versions of the Snowflake driver using a legacy driver class being unable to connect to Flyway

Bug fixes

• drift results were published to Flyway Pipelines even when publishResult was false

• dry runs no longer publish migrate events to Flyway Service as deployments

• Fixed an issue where an unusually long configuration value could cause Flyway's debug configuration table to render incorrectly

• generated migration filename timestamps are now in UTC rather than the local system timezone

Library upgrades

• bump couchbase client to 3.12.3 and databricks-jdbc to 3.4.2

New features

• Added a deployment overview table to the dry run report

• check.code.profile and check.code.profiles let a code analysis run exclude a named set of rules and rule groups, so analysing a schema model no longer reports violations from rules that cannot apply to it. A built-in schemaModel profile is included.

• flyway deploy now publishes the deployment to Flyway Pipelines when publishResult is enabled

Changes

• Added a comment to check dryrun reports when they are truncated

• skip restoring sql server database name and 'ansi_nulls' if they're unchanged

• The JSON report file now carries a top-level schemaVersion field identifying the version of the report format.

Database compatibility

• Snowflake Postgres is now recognised as a supported PostgreSQL-derivative database type

Bug fixes

• Fixed DB2 migrations failing with SQLCODE=-428 when a schema check introduced in a previous release broke the requirement that some statements (e.g. TRUNCATE) be first in a unit of work

• setting url, user or password on an environment using the docker provisioner is now rejected. The provisioner supplies these from the container it starts, and a configured value was silently used by operations that ran without provisioning.

• the cached credentials from flyway auth are no longer invalidated when Flyway is upgraded. Note that upgrading to this version requires running flyway auth once more.

• the docker provisioner's container connection details were discarded when the build environment was resolved without provisioning, so Flyway could migrate and compare against a url left in configuration instead of the container it started.

• the docker provisioner showed the raw Docker CLI error instead of a clear message when the Docker daemon was not running

Library upgrades

• Docker images now run on JRE 25 (previously JRE 21)

• Update upgrade org.eclipse.jetty:jetty-server to 12.1.12

New features

• Flyway debug logs now show the final configuration parameters along with where each value originated

Changes

• Improve dry run script's reviewability by removing unnecessary statements

• the Flyway MCP Server tool "create_before_pull_snapshot" has been renamed to "create_schema_model_checkpoint"

Java compatibility

• jackson-databind is now an optional dependency of flyway-core. If your application or integration relies jackson-databind, you should explicitly declare it as a dependency in your project rather than relying on flyway-core to provide it transitively

• JSON support is no longer bundled with flyway-core and is now provided through the new flyway-core-utilities module

Library upgrades

• Upgraded com.fasterxml.jackson.core:jackson-annotations from 2.21 to 2.22

• Upgraded com.fasterxml.jackson.core:jackson-core from 2.22.1 to 2.22.2

• Upgraded com.fasterxml.jackson.core:jackson-databind from 2.22.1 to 2.22.2

• Upgraded org.mariadb.jdbc:mariadb-java-client from 2.7.13 to 2.7.14

New features

• The Flyway command line and Docker images now automatically use the proxy configured in your operating system. Set the FLYWAY_USE_SYSTEM_PROXIES environment variable to false to disable this.

Changes

• removed the unused g++ compiler toolchain from the Redgate Azure Docker images

Database compatibility

• Issue 4269 Snowflake parser supports AGENT IF EXISTS clause

Bug fixes

• fixed Oracle parser failing with "Incomplete statement" when a PL/SQL package body referenced a table or column literally named CASE after INSERT INTO, UPDATE, JOIN, CREATE TABLE, or AS

• the docker provisioner rejected a sourceEnvironment that declared provisioner = "none", reporting it as already provisioned

Java compatibility

• TOML support is no longer bundled with flyway-core and is now provided through the new flyway-core-utilities module

Bug fixes

• Fixed a bug where Redshift CREATE, ALTER and DROP IDENTITY PROVIDER statements were run inside a migration transaction, which Redshift does not support

Java compatibility

• ConfigurationExtension.copy() no longer requires jackson-databind on the classpath; if it's absent, copy() falls back to a shallow copy

Breaking changes

• JSON results with timestamps now include a UTC offset. Reports generated will not be compatible with previous versions of Flyway. API users relying on getTimestamp or setTimestamp will need to use OffsetDateTime instead

Changes

• Flyway now warns when validate resolves no migrations from the configured locations but the schema history contains applied migrations

• mcp server project load will no longer raise an error if a .conf project was detected in a default location outside of the project root

• OSS no longer recognises the 'publishResult' or 'checkDriftOnMigrate' parameters which had no effect

Bug fixes

• Configuration details defined against a specific environment, such as a custom schema history table or default schema, were lost when Flyway switched to that environment

• The Docker provisioner could not connect to Oracle 23 and later containers, failing with ORA-12514, because it requested the wrong pluggable database service

Java compatibility

• CockroachDB is now provided as a standalone database module. API users targeting CockroachDB should include the new CockroachDB module instead of relying on the PostgreSQL module

Library upgrades

• Upgraded adoptium/temurin25-binaries from 25.0.3+9 to 25.0.4+7

• Updated BouncyCastle to 1.85 to address a High severity Uncontrolled Recursion advisory

• Updated Oracle SQLcl in the Flyway Docker oracle image to 26.2.0.181.2110, resolving CVE-2026-68494 in jackson-core

New features

• deploy command result now includes execution time in milliseconds

• environments_<name><setting> and flyway<setting> environment variables can now use any letter casing in their prefix, e.g. ENVIRONMENTS_PRODUCTION_PASSWORD

Database compatibility

• Databricks Lakebase is now recognised as a supported PostgreSQL-derivative database type in public preview

• snapshot history is now supported on Databricks

Bug fixes

• Databricks identifiers containing a backtick produced invalid SQL

• Databricks migrations could fail at the unlock step with a Delta ConcurrentAppendException; the lock keepalive no longer races the unlock

• Issue 4259 Fixed afterConnect callback not being fired on the migration connection

• Fixed an issue that prevented several after*OperationFinish SQL callback scripts (clean, validate, undo, repair, baseline) from ever running

• Fixed an issue where the Docker provisioner for Oracle would immediately exit

• Fixed dry run failing on Databricks with "Unable to switch connection to read-only" error

Java compatibility

• Issue 4240 Log execution of Java callbacks, matching SQL/script callback logging

Library upgrades

• Upgraded jansi to use org.jline.jansi package

New features

• Add support for new 'IncludeOnlineIndexCreation' option for Oracle

• check drift and check changes JSON output now includes an id for each difference, allowing drift to be resolved against specific objects

• Flyway MCP server now available, exposing development-time tools an AI agent can call. These tools run flyway commands for both state based and migrations projects

Changes

• Include the offending SQL in error messages for Flyway Desktop when debug logging is disabled

• the docker provisioner now reports a dedicated error code when a SQL Server or Oracle container is provisioned without accepting the database vendor's EULA

Bug fixes

• Fixed the 'auth' command incorrectly showing a "no locations configured" warning that only applies to migration commands

Library upgrades

• Updated jackson-databind to 3.1.5 / 2.22.1 to address a High-severity Incorrect Authorization advisory

New features

• Add support for new 'disable-constraints-for-static-data' option for PostgreSQL

Changes

• -h help for migrate, info, validate, clean, and undo now lists relevant configuration parameters and a usage example instead of just a description

• Oracle SQL error output no longer shows the redundant SQL State and Error Code lines, as the ORA-#### code is already in the message

• testConnection now keeps the configured environments available so provisioners that reference another environment (for example the docker provisioner's sourceEnvironment) resolve correctly when testing an inline environment

• testConnection now reports provisioning progress (e.g. Docker container start-up) when progress output is enabled

• the docker provisioner now reports clear, dedicated errors when the Docker CLI is not installed or the Docker daemon is not running

• the legacy compose-file configuration of the preview docker provisioner is deprecated and now logs a warning; use the docker-compose provisioner instead

• using 'auth' without the '-IAgreeToTheEula' flag defaults to an interactive EULA agreement process

Bug fixes

• Fixed an issue where authentication warnings could be displayed multiple times during a Flyway run

• Issue 4253 Fixed FlywayUnknownMigrationTypeException when schema history table contains legacy SPRING_JDBC type from older Flyway versions

Performance improvements

• Improved Flyway CLI cold start time by switching driver JARs from eager static classpath loading to lazy dynamic loading

Library upgrades

• Upgrade Snowflake from 4.0.2 to 4.3.1

New features

• smart docker provisioner keepAlive reuses the build database container across Flyway commands

Changes

• filesystem location 'not found' messages now report the effective working directory and prompt you to check it, since running Flyway from the wrong working directory (without -workingDirectory) is a common cause

• Native Connectors mode is now enabled by default for Cassandra

• outOfOrder mode is now reported at info level instead of as a warning

• The preview docker environment provisioner has been renamed to docker-compose. Existing docker provisioner configurations that use a compose file continue to work via automatic forwarding.

Bug fixes

• A missing callback location (including the default filesystem:callbacks) is now skipped instead of being logged as an error or failing the command

• drift resolution script generation failures no longer fail the check drift command; drift is still reported and any scripts that can be generated are still written

• Fixed drift resolution failing to generate scripts when the drift included object types whose names contain spaces (e.g. user-defined types)

• The smart docker provisioner now starts Postgres and MySQL build containers with valid credentials and a usable default schema, so provisioning and migrating against them succeeds

Performance improvements

• skip building an unused Flyway instance for configuration-only commands (e.g. constructMigrationName, parseMigrationName, comparison-capabilities), reducing their startup latency

Library upgrades

• Upgraded com.fasterxml.jackson.core:jackson-databind from 2.21.2 to 2.22.0

• Upgraded tools.jackson.core:jackson-databind from 3.1.1 to 3.1.4

New features

• Added a check.driftResolutionFolder setting to configure the folder in which drift resolution scripts are generated when drift is detected

• Flyway CLI now exits with a distinct exit code derived from the error code when a FlywayException is thrown

Changes

• check drift, changes and dryrun commands now report phase-level progress when outputProgress is enabled

Bug fixes

• Fix FLYWAY_TOKEN and FLYWAY_EMAIL environment variables not being recognised for PAT authentication

Changes

• Flyway now warns when an offline permit is due to expire within the next 30 days

• Improved progress reporting for PostgreSQL, MySQL and SQLite

Bug fixes

• Oracle EXEC statements preceded by a comment now parse correctly

Java compatibility

• API users now must include a flyway Licensing module dependency to be recognized as Redgate edition

New features

• Flyway can load custom SQLFluff rules for use in the Check command

Java compatibility

• API users are now required to include the flyway-proprietary module to use Redgate proprietary features

Internal dependency

• Upgraded RgCompare to 1.58.2.4353