Since ensuring compatibility with Drupal CMS seemed important enough to ensure with CI, I added `OPT_IN_TEST_DRUPAL_CMS=1` (and associated autorun) to some of my contrib modules’ Weekly scheduled pipelines (see [here](https://git.drupalcode.org/project/searchstax/-/pipelines/876158), for example). However, independent of the module the `build` step fails with the following error: ``` Hint: To allow running the config command recommended below before dependencies are installed, run create-project with --no-install. You can then cd into /builds/project/searchstax/cms, configure allow-plugins, and finally run a composer install to complete the process. In PluginManager.php line 821: symfony/runtime contains a Composer plugin which is blocked by your allow-p lugins config. You may add it to the list if you consider it safe. You can run "composer config --no-plugins allow-plugins.symfony/runtime [tr ue|false]" to enable it (true) or disable it explicitly and suppress this e xception (false) See https://getcomposer.org/allow-plugins ``` This seems to be due to some recent change, the pipeline [worked fine last week](https://git.drupalcode.org/project/searchstax/-/pipelines/867733). Before working around this problem in every module individually, I wanted to ask if this is expected, whether it can maybe be fixed in the templates directly or whether testing Drupal CMS is maybe only supported for Core and not even supposed to be used by contrib modules. (If I’m just supposed to fix this in each module then any pointers on how to best do that would of course also be really appreciated.) Thanks a lot in advance for your help!