- Issue created by @project update bot
- last update
10 months ago 5 pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-185727These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
10 months ago 5 pass - last update
10 months ago 5 pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request (MR) is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-188815These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- last update
10 months ago 5 pass - Status changed to Needs work
24 days ago 11:03am 10 March 2025 - 🇧🇬Bulgaria pfrenssen Sofia
Just updating the version strings is not sufficient. I did a check and the following issues also need to be addressed:
- Class
Drupal\mailgun\Commands\MailgunSanitizeCommands
implements deprecated interfaceDrush\Drupal\Commands\sql\SanitizePluginInterface
: use\Drush\Commands\sql\sanitize\SanitizePluginInterface
instead. - MailgunMail.php, line 111: Call to deprecated method
renderPlain()
. Deprecated in drupal:10.3.0 and is removed from drupal:12.0.0. UseDrupal\Core\Render\RendererInterface::renderInIsolation()
instead.
- Class
- 🇨🇴Colombia diegoluisr
I've created a patch with recomendations from Update Status module.
- 🇺🇦Ukraine knyshuk.vova
knyshuk.vova → made their first commit to this issue’s fork.
- 🇺🇦Ukraine knyshuk.vova
knyshuk.vova → changed the visibility of the branch project-update-bot-only to hidden.
- 🇺🇦Ukraine knyshuk.vova
knyshuk.vova → changed the visibility of the branch 3451175-automated-drupal-11 to hidden.
- 🇺🇦Ukraine knyshuk.vova
Merge request !27
I was able to configure the module and send an email using version 2.0.0 of the module.