GitLab CI pipeline for recommendations broken due to farmos module changes

Root cause found: https://git.drupalcode.org/project/farm_bee/-/commit/9dca67eebd6c7b245b9....

Same problem in https://git.drupalcode.org/project/farm_forest/-/commit/0cf62850304df39c...

One more:

Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - farmos/farmos[2.0.0-alpha1, ..., 2.0.0-beta8.1] require drupal/admin_toolbar ^2.4 -> found drupal/admin_toolbar[dev-2.x, 2.4.0, 2.5.0, 2.x-dev (alias of dev-2.x)] but it conflicts with your root composer.json require (^3).
    - farmos/farmos 2.0.0-rc1 requires drupal/core 9.4.9 -> found drupal/core[9.4.9] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos 2.0.0 requires drupal/core 9.5.0 -> found drupal/core[9.5.0] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos 2.0.1 requires drupal/core 9.5.3 -> found drupal/core[9.5.3] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos 2.0.2 requires drupal/core 9.5.4 -> found drupal/core[9.5.4] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos 2.0.3 requires drupal/core 9.5.5 -> found drupal/core[9.5.5] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos 2.0.4 requires drupal/core 9.5.7 -> found drupal/core[9.5.7] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos[2.1.0, ..., 2.1.1] require drupal/core 9.5.9 -> found drupal/core[9.5.9] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos 2.1.2 requires drupal/core 9.5.10 -> found drupal/core[9.5.10] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos[2.1.3, ..., 2.x-dev] require drupal/core 9.5.11 -> found drupal/core[9.5.11] but it conflicts with your root composer.json require (9.5.8).
    - farmos/farmos[3.0.0-beta1, ..., 3.x-dev] require drupal/core 10.1.6 -> found drupal/core[10.1.6] but it conflicts with your root composer.json require (9.5.8).
    - drupal/farm_maple 2.x-dev is an alias of drupal/farm_maple dev-2.x and thus requires it to be installed too.
    - drupal/farm_maple dev-2.x requires farmos/farmos ^2 || ^3 -> satisfiable by farmos/farmos[2.0.0-alpha1, ..., 2.x-dev, 3.0.0-beta1, 3.0.0-beta2, 3.0.0-beta3, 3.x-dev].
    - Root composer.json requires drupal/farm_maple 2.x-dev -> satisfiable by drupal/farm_maple[2.x-dev (alias of dev-2.x)].

Green! 🚀

This is one of the most common changes necessary to AM:A's recommendations. Tagging and explicitly documenting the pattern.

ℹ️ These (drupal/farm_bee and others, see #4 and #5) are modules in the so-called generated recommendations. These are automatically generated from drupal.org and have not been vetted. That is what happened here. The only possible fix is to override them, by adding them as a curated recommendation. Either by recommending the user to install it manually (which we did here, since it's a very rarely used module), or by pinning to a specific version.

Automatically closed - issue fixed for 2 weeks with no activity.