The target version up to which Flyway should consider migrations. If set to a value other than current or latest,
this must be a valid migration version (e.g. 2.1).
When migrating forwards, Flyway will apply all migrations up to and including the target version. Migrations with a
higher version number will be ignored. If the target is current, then no versioned migrations will be
applied but repeatable migrations will be, together with any callbacks.
When undoing migrations, Flyway will apply all undo scripts up to and including the target version. Undo scripts with a lower version number will be ignored. Specifying a target version should be done with care, as undo scripts typically destroy database objects.
Special values:
current: designates the current version of the schemalatest: the latest version of the schema, as defined by the migration with the highest versionnext: the next version of the schema, as defined by the first pending migration<version>?: Flyway Teams Instructs Flyway to not fail if the target version doesn’t exist. In this case, Flyway will go up to but not beyond the specified target (default: fail if the target version doesn’t exist) (e.g.) target=2.1?latest for versioned migrations, current for undo migrations.
./flyway -target="2.0" migrate
flyway.target=2.0
FLYWAY_TARGET=2.0
Flyway.configure()
.target("2.0")
.load()
flyway {
target = '2.0'
}
<configuration>
<target>2.0</target>
</configuration>