3.1.0

• Allow laravel-doctrine/orm 2.0
• Laravel 10 #131 @77web

3.0.0

• Laravel 9 support thanks to @seifane-wise! #118
• Require doctrine/migrations 3

Breaking changes

• If you have set version_column_length in your configuration, make sure this is large enough to
  fit the new value used in version column, new default is 191.
• Rename of command options.
  All commands are now directly used from the doctrine/migrations library. This causes several changes in how
  you might have used the commands, some options have been renamed, some removed, some added.
• New configuration structure, we now support all the same configuration keys as doctrine/migrations.
  See default config for new structure. Note that laravel-doctrine/migrations allow different config
  for each EntityManager.

Please read the upgrade guide from doctrine/migrations here: https://github.com/doctrine/migrations/blob/3.5.x/UPGRADE.md
Your previous doctrine/migrations version was 2.x.

2.3.0

• Support Laravel 6, 7 and 8 with PHP 8.

2.1.0

• Possible to configure version column length with version_column_length in config/migrations.php. #96 @chewbakartik

2.0.0

• Laravel 7.0 support thanks to @chewbakartik! #95

Breaking changes

You will need to update your migration files.

• Doctrine\Schema\Schema -> Doctrine\DBAL\Schema\Schema
• Doctrine\DBAL\Migrations\AbstractMigration -> Doctrine\Migrations\AbstractMigration
• up and down methods needs the void return type.

1.3.2

• Added organize_migrations which lets you organize by year, or year and month. #91 (@FlashBlack)

1.3.1

• Fix: #89 Call to undefined function str_contains() (@dextercampos)

1.3.0

Laravel 6

v1.2.0

Fixed ResetCommand table isolation issues for postgresql and mssql (#…

v1.1.10

#70: Fix --no-interaction for VersionCommand (#71)