Require correct Neos version

[baschny]

In my project we have Neos 2.3 and thus Flow 3.3 (still known as typo3/flow).

In the requirements of neos/behat we have "neos/flow": "*" which will thus fetch the latest neos/flow parallel to my currently installed typo3/flow.

Wouldn't it be safer to specify the minimum required Flow version (where the namespace renaming has happened already)? It crashes than on the "require_once" which in newer versions tries to load from the Neos.Flow instead of TYPO3.Flow (as I still have it).

My solution would be to hardcode the latest version that is compatible: "neos/behat": "~2.4".

Or should I stick to using the "deprecated" flowpack/behat instead?

[albe]

Sorry for being late with a reply. Indeed, we should be stricter with the required flow versions. I guess there's two things preventing us:

• we currently rely on the convenience of always only requiring a new neos/behat version in Flow/Neos dev distributions when something changes, so we need this package to be installable with Flow versions "into the unknown future"
• we do not have an automatism to update the required Flow version in place, this would need to be handled in https://github.com/neos/flow-development-distribution/blob/master/Build/set-dependencies.sh

I guess you already did what you suggested and pinned the behat version. That is a sane workaround for now, since this package is not changing frequently so that you would miss out on anything. I'll create an issue to handle this for the future, though that will not fix the issue with existing neos/behat versions.