Support Drush 12 and above only

I think this is required to be resolved for Drupal 11 compatibility, so therefore marking it as a blocker for a stable Feeds release.

@jcventura said on Slack he's planning to look at this issue.

I see that at least drush feeds:list still works on Drupal 11. So if all Drush commands still work as intended on Drupal 11, then this issue would no longer be a release blocker.

It would be good to try each command manually to be sure.

I tried all commands below and they still work on Drupal 11 as intended. So this is no longer a release blocker. It is now "a nice to have" and can also be done at a later time. I'm tagging this as an intermediate issue and will add it to 🌱 [meta] Feeds intermediate issues Active .

  feeds:disable     [feeds-dis] Disable a feed specified by its id.
  feeds:enable      [feeds-en] Enable a feed specified by its id.
  feeds:import      [feeds-im] Import a feed specified by its id.
  feeds:import-all  [feeds-ima] Import all feeds.
  feeds:list-feeds  [feeds-lf] Display all feeds using a drush command.
  feeds:lock        [feeds-lk] Lock a feed specified by its id.
  feeds:unlock      [feeds-ulk] Unlock a feed specified by its id.

To address the compatibility issues with Support Drush 12 and above only, please update your composer.json file with the following changes.

"require-dev": {
"drupal/pathauto": "dev-1.x",
"drush/drush": " ^12 || ^13"
},

I'm using drush version 13.0.1.0 and tried to run all feeds command & it is working fine.

Once we update the namespace as mentioned in drush 12 then we have to add conflict in the composer.json
Also it would be great if we update the commands as per php attribute instead of document annotation.
@megachriz what are your thoughts on this? If you consider this then we need to update the summary.

We could be using php attributes if:

• That would work on Drupal 10.2, because that version is still officially supported;
• That would work on PHP 8.1.

If it works too on Drupal 10.1, that would be cool, but since 10.1 is no longer officially supported, this is less important. We should only test it once to see if we are required to raise the requirements.