Skip to content

Instantly share code, notes, and snippets.

@kdambekalns
Last active August 29, 2015 14:22
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kdambekalns/186f2c5237ab1bfd7c8e to your computer and use it in GitHub Desktop.
Save kdambekalns/186f2c5237ab1bfd7c8e to your computer and use it in GitHub Desktop.
Solving issues with Neos 1.x or Flow 2.x and doctrine/migrations

Flow has always used doctrine/migrations as dev-master. Now a 1.0 release of the migrations package is approaching and some breaking changes spoil the fun. See these issues for some details:

The typo3/flow package has been updated and new 2.x releases have been tagged. But you need to make sure your root manifest (composer.json) is requiring the correct version of doctrine/migrations as well. It should be pinned to the last version that is known not to conflict with the other dependencies of Flow.

Below is what you must require instead of anything else (like @dev or dev-master).

"doctrine/migrations": "1.0.0-alpha3"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment