docs

Resources/doc/Cookbook/reusable_migrations.md

@@ -6,7 +6,7 @@ This is often done via copy-pasting-then-modifying the same migration steps into
 migration logic to apply is quite complex, this can result in a tedious and brittle process, as it is easy to forget to
 change a reference or other parameter.
 
-Since version 6.3, it is possible to achieve the same result in an easier way, with less chances for manual error.
+It is possible to achieve the same result in an easier way, with less chances for manual error.
 The process is:
 
 1. create the "core" migration definition, save it in separate folder, eg. a subfolder of the `MigrationsVersions` one.

WHATSNEW.md

@@ -5,12 +5,15 @@ Version: 1.0.1
 
 * 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`
 
+
 Version: 1.0
 ============