prepare 4.5 release

.travis.yml

@@ -39,9 +39,9 @@ matrix:
     - php: 7.2
       env: EZ_PACKAGES='ezsystems/ezplatform:~1.11.0 ezsystems/ezplatform-xmltext-fieldtype:^1.3 ezsystems/behatbundle:^6.5 netgen/tagsbundle:~3.0' EZ_VERSION=ezplatform EZ_APP_DIR=app EZ_KERNEL=AppKernel CODE_COVERAGE=0 INSTALL_TAGSBUNDLE=1
 
-  #allow_failures:
-    # this currently fails because of the refactoring of location matcher
-    #- php: 5.4
+  allow_failures:
+    # this currently fails because of... composer dying ?
+    - php: 5.6
 
 before_install:
   # No need for a web server, until we start testing using Selenium

README.md

@@ -167,6 +167,7 @@ In a Yaml migration, you can define the following types of actions:
 - purging and recovering Contents from the Trash
 - creation, appending, copy, renaming and deletion of files
 - execution of command-line scripts
+- execution of methods of symfony services
 - execution of http calls
 - sending of email
 - canceling, snoozing or suspending the migration itself
@@ -218,6 +219,9 @@ For a more detailed example of a migration definition done in PHP, look in the M
 standard autoloading mechanism of the application does not apply when loading the migration definition. This is also
 the reason why the php classes used as migrations should not use namespaces. 
 
+*NB* since version 4.5, it is also possible to run any method of any existing Symfony service just by declaring it as
+migration step in a yaml migration. See the [relevant DSL](Resources/doc/DSL/Service.yml) for details.
+
 ### Re-executing failed migrations
 
 The easiest way to re-execute a migration in 'failed' status, is to remove it from the migrations table:

WHATSNEW.md

@@ -1,7 +1,10 @@
-Version 4.5 (unreleased)
-========================
+Version 4.5
+===========
 
-* New: allow resolving references for the `filename` element of steps reference/load and reference/save
+* New: allow resolving references for the `filename` element of steps `reference/load` and `reference/save`
+
+* New: migration step `service/call` allows to call a method on any existing Symfony Service, and set a reference to the
+    result
 
 
 Version 4.4
@@ -12,7 +15,6 @@ Version 4.4
 * New: the element `remove_drafts` can be used for migration steps of type ContentType/update to make sure that any
     existing drafts of the given ContentType are removed
 
-
 * New: support the value '*' for the `remove_attributes` parameter in ContentType definitions. This allows to remove all
     the attributes which already exist in the ContentType, except for the ones defined in the `attributes` parameter