- Issue created by @project update bot
- Open on Drupal.org βCore: 10.2.x + Environment: PHP 8.1 & MySQL 5.7last update
9 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-120835This 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.x + Environment: PHP 8.1 & MySQL 5.7last update
9 months ago Waiting for branch to pass - First commit to issue fork.
-
shelane β
committed 047b47d7 on 4.x authored by
Project Update Bot β
Issue #3428968: Automated Drupal 11 compatibility fixes for...
-
shelane β
committed 047b47d7 on 4.x authored by
Project Update Bot β
- Status changed to RTBC
4 months ago 4:55am 23 August 2024 Hello,I have tested the MR 13 and haven't found any depreciated function using the upgrade status module. The MR is working fine in Drupal 11,I think it's now ready for Drupal 11 release, moving this ticket to RTBC.
Thank you- Status changed to Fixed
4 months ago 12:15am 26 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.