5.8.0

• New: the content_type/update migration step now accepts the default_always_available element (issue #189)

• New: the kaliop:migration:generate command now accepts a -a flag to allow specifying custom admin users (issue #187)

• Fix: usage of the -a flag when running kaliop:migration:mass_migrate and when running kaliop:migration:migrate -p was not propagated to subprocesses

• Fix: the if element was not giving a fatal error for all migration steps affecting repository elements (Content, Location, etc...), at least for Symfony version 2.7.10

• New: the kaliop:migration:migrate and kaliop:migration:mass_migrate now accept a --force flag that will execute migrations that were previously executed or skipped or failed.
  NB this flag is useful when testing migrations, but should be used sparingly in production context, as replaying migrations that had already been executed can wreak havoc to your database. you have been warned

• BC changes:

  • the kaliop:migration:generate command now uses as default language for the generated migrations the default one of the current siteaccess, instead of 'eng-GB'