Releases: laravel-doctrine/migrations
Releases · laravel-doctrine/migrations
3.3.0
What's Changed
- Hotfix/orm 3 by @TomHAnderson in #136
New Contributors
- @TomHAnderson made their first contribution in #136
Full Changelog: 3.2.0...3.3.0
3.1.0
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 thedoctrine/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 thatlaravel-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
2.1.0
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
anddown
methods needs thevoid
return type.
1.3.2
1.3.1
1.3.0
Laravel 6
v1.2.0
Fixed ResetCommand table isolation issues for postgresql and mssql (#…