- Issue created by @mstrelan
- 🇮🇳India Rajan Kumar@2026
Rajan Kumar@2026 → made their first commit to this issue’s fork.
- Open on Drupal.org →Core: 10.1.4 + Environment: PHP 8.2 & MySQL 8last update
about 1 year ago Waiting for branch to pass - Status changed to Needs review
about 1 year ago 5:48am 7 May 2024 - Open on Drupal.org →Core: 10.1.4 + Environment: PHP 8.2 & MySQL 8last update
about 1 year ago Waiting for branch to pass - 🇮🇳India Rajan Kumar@2026
Hellow, @mstrelan @quicksketch
Added Drupal version for 11
I have created MR , please kindly review it once.
- Status changed to Needs work
about 1 year ago 6:26am 7 May 2024 - 🇦🇺Australia mstrelan
@Vighneshh we need some kind of backwards compatibility, will need more thought than simply changing the namespace. Also the screenshots are not helpful and I'm sure the maintainer would prefer merge requests over patches.
@Rajan Kumar@2026 that is not in scope here.
- 🇦🇺Australia mstrelan
mstrelan → changed the visibility of the branch 3445590-compatibility-with-drush to hidden.
- First commit to issue fork.
- 🇦🇺Australia sime Melbourne
Thoughts
What is the minimum version of drush required by webform? Because we should convert commands to PHP8 annotations and drop the drush.services.yml.
If annotations allow to specify compatibility with a version of drush, then make a deprecated command file for drush <=12 and keep the current one (with the fix) for >13.
- 🇵🇹Portugal jcnventura
Simplest way to solve this issue is to fix it in Drush. Please upvote my request: https://github.com/drush-ops/drush/issues/6018
- 🇦🇺Australia sime Melbourne
https://github.com/drush-ops/drush/pull/6019 per @moshe's suggestion.
- Status changed to Closed: works as designed
5 days ago 1:13pm 24 July 2025 - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
If I am reading things correctly, compatibility was restored in 13.6.0; see:
https://github.com/drush-ops/drush/commit/34cc1cc0456be20b7710e53b3b1c4a...