[debug] <module> commands loaded even though its constraint (^9 || ^10) is incompatible with Drush <v.m.n.> Broaden the constraint in modules/contrib/<module>/composer.json (see 'extra\drush\services' section) to remove this message.
This error message doesn't happen any more with Drush 12. Why?:? But in the Drush -vvv header message there is only one line like,
[debug] Found drush.services.yml for migrate_tools Drush commands
Looking at the composer.json of the corresponding module, at the line associated to the problem, this is,
"drush.services.yml": ">=9"
That allows the use of any new Drush version. For other concerned modules with Drush 11 in our Drupal configuration, that is rather,
PB: "drush.services.yml": "^9 || ^10"
OK: "drush.services.yml": "^9 || ^10 || ^11"
Hence we think,
- Drush 12 bypass the problem.
- Each concerned module should have a Drush message,
[debug] Found drush.services.yml for <modules> Drush commands
- The silence on the Drush problem creates a confusion between modules without and with a Drush service and a compatibility problem with the Drush version used. Such a message could be useful to easily know modules with a Drush service.
Question:
- Does the Drush anomaly message should by bypassed?
- Should be asked to developers to update their module code to adapt it to a new Drush version?
drush cr
drush -vvv
Active
Code