1.0.4

• Fixed: migration definitions in stock locations would not be detected any more and had to be passed using an absolute path (bug introduced in rel. 1.0-beta1).
  NB: if you had executed migration 20220101000200_FixExecutedMigrationsPaths.php in between version 1.0-beta1 and 1.0.4, please check manually in the database migrations table to see if there are any migrations with a relative path which starts at the wrong directory (one level up from the project dir).

• Fixed: test suite failing with recent eZPlatform 3.3 versions

• Fixed: exception thrown at end of migration if the migration steps include sql executing transaction commits, such as f.e. creation of a table with databases such as mysql and oracle (PR #25)

• Fixed: correctly abort a migration when it leaves a database transaction pending (nb: this can be detected only for transactions started using Doctrine, not for transactions started using sql begin statements)

• Improved: reporting of errors happening before/during/after migration execution, esp. anything related to transactions

• Improbved: when generating migrations, try harder to reset the repository to the originally connected user in case of exceptions being thrown

BC notes (for developer extending the bundle):

• MigrationService::getFullExceptionMessage gained a 2nd parameter: $addLineNumber = false
• AfterMigrationExecutionException produces a different error message when passed 0 for the $step parameter
• service ez_migration_bundle.migration_service requires an added setConnection call in its definition