Releases: doctrine/DoctrineORMModule
Releases · doctrine/DoctrineORMModule
 3.1.3
Changed
- Doctrine 2 and future versions will be referred to as just Doctrine
 
3.1.2
Added
- Enable support for doctrine/persistence 2.0 or 1.3
 
3.0.9
Added
- Enable support for doctrine/persistence 2.0 or 1.3
 
3.1.1
Fixed
- The 
doctrine/migrationsmodule defaults theorganize_migrationsconfiguration values$this->migrationsAreOrganizedByYearand$this->migrationsAreOrganizedByYearAndMonthto false which puts all migrations into a single directory. If theorganize_migrationsis set toyearoryear_and_monthit cannot be unset to false. So, this module has removedorganize_migrationsfrom the defaultorm_configmigrations configuration. 
3.1.0
Added
- Support for Migrations ^3.0
 
Removed
- Support for Migrations 1 and 2
 
3.0.8
Fixed
- v3.0.7 introduced the ability to have migrations for multiple object managers. This change overlooked the case where a developer did not install the optional 
doctrine/migrationsrepository and caused an error when trying to load the module. This release adds specific unit tests for optional dependencies and fixes the break in v3.0.7. 
3.0.7
Added
- Support for multiple migrations configurations. For the life of this module support for migrations has been limited to 
doctrine.entitymanager.orm_default. With this release you can create migrations configurations for multiple object managers. You are however limited to only one configuration per object manager. 
3.0.6
3.0.5
Fixed
- Newer Doctrine coding standard flagged nesting of control structures per method as small as possible.
 
Removed
- Added conflict to composer.json for doctrine/migrations >= 3.0
 
3.0.4
Changed
- Use CodeCov instead of Scrutinizer