Active
Project:
Feeds
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Jun 2024 at 15:49 UTC
Updated:
29 Nov 2024 at 10:40 UTC
Jump to comment: Most recent
Since:
Drush versions below 12.4.3 are incompatible with Drupal 10.2.
(as per drupal 10.2.0 release notes)
module's Drush commands could perhaps be updated according to:
https://www.drush.org/12.x/commands/.
drush.\Drupal\Tests\feeds\Functional\Commands\FeedsDrushCommandsTest.Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
ankitv18 commentedComment #3
ankitv18 commentedComment #4
megachrizI 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.
Comment #5
ankitv18 commentedComment #6
megachrizI see that at least
drush feeds:liststill 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.
Comment #7
megachrizI 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 #3165018: [meta] Feeds intermediate issues.
Comment #8
rajan kumar@2026 commentedTo 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"
},
Comment #9
ankitv18 commentedI'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.
Comment #10
megachrizWe could be using php attributes if:
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.
Comment #11
megachrizI added a list of tasks to the issue summary that could help with fixing this issue.