Problem/Motivation

Drush error,
[debug] search_api commands loaded even though its constraint (^9 || ^10) is incompatible with Drush 11.4.0.
Broaden the constraint in modules/contrib/search_api/composer.json (see 'extra\drush\services' section) to remove this message. [0.24 sec, 12.26 MB]

The numbers refer to Drush version and not Drupal.

Steps to reproduce

drush cr
drush -vvv

Proposed resolution

A change like,
"drush.services.yml": "^9 || ^10"
->
"drush.services.yml": "^9 || ^10 || ^11"
in search_api/composer.json

Remaining tasks

Comments

Chris64 created an issue. See original summary.

drunken monkey’s picture

Version: 8.x-1.28 » 8.x-1.x-dev
Component: General code » Drush / Rules
Status: Active » Postponed (maintainer needs more info)

Thanks for reporting this problem. However, I fear I cannot reproduce it. I run Drush 11.5.1, but get no such warnings (even with -vvv).
Do you have a link to some documentation for the composer.json entry? If that indeed reflects the Drush version, then I guess it would still be correct to update it, even if we’re not sure it causes problems. (Perhaps Drush removed that check again since 11.4.0?)

chris64’s picture

Done again. The message is gotten:

  [debug] search_api commands loaded even though its constraint (^9 || ^10) is incompatible with Drush 11.5.1. Broaden the constraint in modules/contrib/search_api/composer.json (see 'extra\drush\services' section) to remove this message. [0.25 sec, 12.41 MB]

So the information is still here with Drush 11.5.1. The Drupal version is 10.0.7. A drush cr is needed before a drush -vvv. This message doesn't appear after a second drush -vvv. Indeed, interesting to know if some others have this.

chris64’s picture

@drunken monkey more information about the module version used: 8.x-1.29.

  • drunken monkey committed e0de2d46 on 8.x-1.x
    Issue #3332036 by drunken monkey, Chris64: Fixed too narrow Drush...
drunken monkey’s picture

Status: Postponed (maintainer needs more info) » Fixed

Thanks for keeping up your work on this. Not sure what changed, maybe I did something wrong the first time, but this time I could indeed reproduce that warning. I therefore committed your suggested change.
Thanks again!

Status: Fixed » Closed (fixed)

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