Releases: doctrine/migrations
1.3.1
For this release, I want to tank @ReenExe for his refactoring effort of the code and @rcatlin for spotting and fixing a non obvious bug.
All the change of this release are included down bellow.
Fixed
- 433: Fix: ExecuteCommand by making sure that it autoload the versions
- 434: Fixing an issue in the order at which some configuration key are loaded
Changed
Added
1.3.0
This release feature in particular a dramatical speedup for all those that have numerous tables/fields in the database that they try to migrate.
I want to particularly thanks @stof and @Ocramius for their continuous support and code review without which you wouldn't have that 97% speedup.
To be more precise, the improvement concern the schema object that is passed to each migrations. That object needs to be rebuild for every migrations. The more fields/table you have in your database the longer it takes. As of now doctrine migrations won't build the schema object until you use it. So if you don't use it you gain 100% of the build time of that object.
Fixed
- 421: Fix issue with some method when the migrations were not loaded
- 405: Correcting composer constraints: allowing PHP 7, dropping 5.4 support
- 406: putting the composer.json back in the archive
Changed
- 233: Separate Configuration Objects from Configuration File Loading
- 407: Replacing the Schema by a proxy
- 422: Refactor the getConnection into a chainloader
- Dropped the support for php 5.4
- Again make the phar more than 3 times smaller
Added
1.2.2
Bugfix:
The outputed sql that keeps track of the run migraitons, wasn't taking into account the configurable column name of the the version table.
Thanks to @scrutinizer for the report that pointed the issue.
1.2.1
Bugfix:
That bug was causing the outputed sql file to be mostly empty.
Thanks to @Binary010100 and @nassuf for the report.
1.2
[1.2.0] - 2015-12-15
Fixed
- fix "all migrated versions shown as unavailable executed"
- Prevent the use of 0 as migration name as it is used internally and conflict
- composer: drop symfony/console from suggested packages, since it's required package
- fix spaces and complete missing file-docblocks
- RecursiveDirectoryIterator don't obtain some order of the file list.
- Fix the yml parser issue with unescaped backslash in double quoted string
Changed
- Adding compression to the generation of the phar
- tests: move autoload of tests to composer
- travis: drop PHP 7.0 from allowed failures, it passes well
- Revert the use of exec to run sql queries
Added
1.1.0
Features:
- Added the possibility to register the configuration as a console helper
- Added support for loading configuration from JSON files
- Added support for loading configuration from PHP files returning an array
- Added the ability to auto create migrations in a folder by month and year
- Added the possibility to inject the OutputWriter after instantiation
- Added the
--allow-no-migration
option to avoid throwing an exception if no migrations are found
Bugfix:
- Switch unexisting
<warning>
tag to<comment>
in the console output
Misc:
- Dropped support for PHP 5.3
- Keep the license file in downloadable archives
- Compressed the phar file that is now half the size that it was.
First stable release of doctrine migrations ! Champagne
There are very few change in stable release compare to the last and only RC.
Doctrine migrations can be used easier as a library since thanks to @dotEvan composer is now aware of the bin file entry point.
Github now build the archive used by composer without all the tests and the build artefacts.
Enjoy
First release candidate of the v1 of doctrine migrations
This release has been made extra small by removing all the dev dependencies.
It should be checked to make sure I didn't brake any feature doing so.
v1.0.0-alpha3
Third (late) alpha of Doctrine migrations
v1.0-ALPHA2
Second (late) alpha of Doctrine migrations