Flex now try to auto discover bundle classes not only for symfony-bundle packages.

Ref #612

FYI. If you need something to keep your (use an) CA bundle up-to-date have a look at https://github.com/paragonie/certainty/ 👍

In the meantime, to fix the issue, constraint symfony/flex version to 1.6.2.

I can confirm this. To repeat:

composer create-project symfony/skeleton ca-bundle-recipe-bug
cd cd ca-bundle-recipe-bug
composer require composer/ca-bundle

And then the error:

Ping @SerheyDolgushev do you have any ideas on how this might be fixed?

Btw - this is affecting blackfire/php-sdk, as it requires composer/ca-bundle.

The new detection of bundle classes in any package type might require adding a validation that the detected class is actually a class implementing the Symfony BundleInterface, and not a random class with a name ending with Bundle.

Making the assumption that a class ending with Bundle in a symfony-bundle package is actually a Symfony bundle could be considered OK. But removing the restriction on the package type makes it much harder to justify this.

If we decide we don't want to implement such validation because broken cases would be very few, we could probably solve it by adding an explicit recipe for composer/ca-bundle forcing to define an empty array of bundle classes (which will disable the automatic detection).

See #627

I've just tagged 1.7.1 with the fix.