- Issue created by @project update bot
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
10 months ago Waiting for branch to pass This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request 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, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
10 months ago Waiting for branch to pass - 🇬🇧United Kingdom darren.fisher
This looks like a straightforward change. Tested on D11 using the MR and all looks good to me.
- 🇩🇪Germany a.dmitriiev
+1 for adding Drupal 11 support and creating a new release.
- First commit to issue fork.
-
renatog →
committed c339eca5 on 2.0.x authored by
project update bot →
Issue #3430379: Automated Drupal 11 compatibility fixes for...
-
renatog →
committed c339eca5 on 2.0.x authored by
project update bot →
- 🇧🇷Brazil renatog Campinas
Seems good
Merged to the dev branch
Thanks everyone
Automatically closed - issue fixed for 2 weeks with no activity.