Closed (fixed)
Project:
Webform
Version:
6.3.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Jul 2025 at 10:17 UTC
Updated:
28 Jan 2026 at 18:46 UTC
Jump to comment: Most recent
After updating the Webform module to the latest version (6.3), an issue occurs when executing Drush commands. The problem did not exist in the previous version and appeared immediately following the update.
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
hamzadwaya commentedComment #4
hamzadwaya commentedComment #7
hamzadwaya commentedComment #8
liam morlandWhat version of Drush are you using? I think you are using an old version.
The merge request reverses a change made in #3477942: Fix phpstan errors.
Comment #9
grzesag commentedI had the same error after upgrading webform to 6.c and running drush updb:
1. Drupal 10.5
2. drush version 12
Fix for me:
1. upgrade drush to version 13
with drush v13 drush updb worked for me
Hope it is useful
Comment #10
vladimirausPR fixes the error.
Comment #11
liam morlandI think the solution is to use a newer version of Drush or an older version of Webform.
Comment #12
hosterholzThis is a breaking change. I think it should be reverted.
If Webform stays incompatible with Drush 12, it should add the conflict property to composer.json to prevent the error.
Comment #14
mrdalesmith commentedHit this same issue and would agree that whilst Drupal 10 and Drush 12 are still supported, this is a breaking change and either needs reflecting as such in a new D11 only release or reverting in the 6.3 releases.
Update to Drush 13 does fix the issue, if that's something you can do.
Comment #15
mrdalesmith commentedI'm knocking this back to Needs review as no approach has been agreed, or any confirmation that either patch fixes the issue. I think the test fails are unrelated but it might be worth looking into them as well.
Comment #16
liam morlandIt looks to me like declaring the conflict, as described in #12, is a good approach.
Comment #18
tonypaulbarkerForgive me if I don't have the logic correct in my mind.
If we add a conflict and release it, what will prevent projects getting the latest resolved version that contains the bug but not the conflict entry?
Comment #21
hosterholz#18 is right. If Webform 6.3.0-beta4 is conflicting with Drush 13, Webform 6.3.0-beta3 would still be installed in an Environment with Drupal 10 and Drush 12. Drush 13 requires PHP 8.3. It cannot be used where PHP 8.3 is not available.
The changed interface should be reverted to
Drush\Drupal\Commands\sql\SanitizePluginInterfacewhich is deprecated in Drush 13. It could be changed afterwards while declaring a conflict to Drush <13 at the same time.Comment #24
liam morlandThanks everyone!
Comment #27
finn lewisHe folks,
Great to see this is fixed, thank you so much!
I just ran into the bug trying to install LocalGov Drupal Microsites.
Any chance of a quick release so we don't have to pin or patch webform?
Many thanks,
Finn
Comment #28
liam morlandwebform 6.3.0-beta4 released.
Comment #29
finn lewisA-MAY-ZING!!!
Thanks Liam!
That's saved us a bunch of working around.
Thank you ever so much :)
Comment #31
liam morlandShould we be declaring an incompatibility with Drush 14?