* Provide another option validationGroups.
* Allow each validation entry to be executed only for matching
validation groups.
* Necessary for the same reason as documented in flow documentation. It
should be possible to execute different validation rules for the same
name or class, only at some points, e.g. at a specific action.
Migrate bootstep names.
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Migrate usages of the path [TYPO3][Flow][Security][Authentication] to
[Neos][Flow][Security][Authentication]
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Migrate name for the media image size cache
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.Fluid" to
"Neos.FluidAdaptor".
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.SwiftMailer" to
"Neos.SwiftMailer".
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to Neos\Flow\Utility\Unicode adjustment
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.Media" to "Neos.Media"
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to Imagine Renaming
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to Eel Renaming
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to cache extraction
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "Neos.Flow.Utility.Files" to
"Neos.Utility.Files" and other extractions of the "Utility" packages.
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjusts code to package renaming from "TYPO3.Flow" to "Neos.Flow"
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust to the renaming of the Object namespace in Flow 4.0
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust to the renaming of the Resource namespace and class in Flow 4.0
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
Adjust "Settings.yaml" to new "requestPattern" and "firewall" syntax
(see FLOW-412)
Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
