0.7.0

• fix: allow setting up the Legacy Bridge along with eZPlatform version 1 - it would work only with eZPlatform 2 beforehand

• fix: when the teststack is used to test a pure legacy extension (ie. not one within a bundle), it would hang at the phase of generating legacy autoloads. We now prevent it from scanning the vendors folder

• improved: when TESTSTACK_APP_DIR is not defined in the config file, the teststack command now tries to find the directory where the application (eZ bundle or legacy extension) is located by looking for a composer.json file first in the parent directory of the test stack itself (for BC), then in the directory of the config file and going up in all its parents, until one is found. The directory being used can be printed out by using the -v cli option

• changed: in the test container, the dir where the project is installed is now /home/test/workspace - it was previously /home/test/bundle

• new: command teststack start learned option -f, which was already supported by teststack build