1.0.5

• Fixed: the --admin-login option had been broken for migrate commands since version 1.0

• port fix for error reporting for after-migration errors to mass_migrate command

• make php step executor handle php Errors besides Exceptions

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

1.0.3

Fixed default migration 20220101000200_FixExecutedMigrationsPaths.php. Thanks @McLone

1.0.2

Fixed php warning in class PHPExecutor due to trait being used twice

1.0.1

• Fixed an exception when throwing an exception in ContentManager

• Fixed: MigrateCommand was setting custom reference values twice when used with --set-reference

• Fixed: php warning when generating Role migrations for roles with policy limitations

• Fixed: in rare circumstances (having two siteaccesses configured with the same repo and root node, but different languages), the TagMatcher could use the wrong language when matching by tag keyword

• BC change (for developers extending the bundle): class TagMatcher changed its constructor signature. the same applies to service ez_migration_bundle.tag_matcher

1.0.0

This release is aligned with kaliop/ezmigrationbundle rel. 6.3.0.

• New: migration step migration_definition/include. This allows one migration to basically include another, the same way it is possible to do that in php.

  It is useful for scenarios such as fe. creating a library of reusable migrations, which can be run multiple times with different target contents every time. This is often achieved by copy-pasting the same migration logic many times.
  As an alternative it is now possible to create a "library" migration, driven by references, and store it only once, in a separate folder, then create many "specific execution" migrations which set up values for the required references and include the library migration's definition.

  Please note that migrations which rely on external resources, such as in this case would be the included migration, go against the principle of migrations being immutable for ease of replay and analysis.

  Ex:

    -
        type: migration_definition
        mode: include
        file: a_path
  

• Improved: when executing migrations with the set-reference cli option, the injected references will be saved in the migration status

• BC change (for developers extending the bundle): method MigrateCommand::executeMigrationInProcess changed its signature

• BC change (for developers extending the bundle): Migrationservice methods executeMigration, executeMigrationInner and resumeMigration now have a different signature. Migrationservice::migrationContextFromParameters has been dropped

1.0 beta 1

• New: implemented all changes which were implemented in the kaliop/ezmigrationbundle version of this tool between releases 5.15.1 and 6.2.1. The list is too long to be copied verbatim here; it can be found online at https://github.com/kaliop-uk/ezmigrationbundle/blob/main/WHATSNEW.md

• Fixed: when generating contentType migrations, do export the is-thumbnail attribute for Content Type Fields, and the Content Type's default_always_available, default_sort_order and default_sort_field

1.0 alpha 3

• New: support is-thumbnail attribute for Content Type Fields

• Fixed: one php exception upon throwing an exception (for bad content_type/create steps)

• Fixed: support for php 8.0 - replace catching \Exception with \Error in places required to make testsuite pass, fix
  a problem with null RelationList fields

• Fixed: when setting references to a ContentType sorting attributes, numeric values were used instead of their string representation

• Moved from Travis to GitHub Actions for testing. Test with all eZ versions from 3.0 to 3.3

1.0 alpha 2

• Fixed one php warning

• Fixed composer dependencies: we need doctrine/dbal 2.11 or later

1.0 Alpha

Explanation of the 'aplha' tag:

1. the codebase itself is fairly stable and complete, as it is a fork of a project which had well over 100 releases already
2. on the other hand, given that the underlying cms framework has evolved a lot, there might be bugs due to API changes
3. also, not all features of the underlying cms framework are fully supported

Known bugs and missing features:

• migration step language/delete is currently broken due to upstream bug https://issues.ibexa.co/browse/EZP-32349
• see #4 for missing features

BC guarantees on the road to 1.0 release:

• the current yml migration format will be kept stable (possibly parts of it deprecated, though)
• the cli commands api will be kept stable
• the php classes and services will surely be heavily refactored. Please no subclassing / injecting them in your code for now

BC with eZMigrationBundle:

See ezmigrationbundle_to_ezmigrationbundle2.md
for all API changes if you are used to eZMigrationBundle 1.