- Issue created by @project update bot
- Open on Drupal.org โCore: 9.5.x + Environment: PHP 7.4 & 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 (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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Open on Drupal.org โCore: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
10 months ago Waiting for branch to pass - ๐ฎ๐ณIndia rahul1707
rahul17 โ made their first commit to this issueโs fork.
- ๐ฎ๐ณIndia patelh84
Verified MR !5 with Drupal 10 and Drupal 11, functionality is working as expected and module is compatible with Drupal 11.
Moving this to RTBC.
- First commit to issue fork.
-
kuhikar โ
committed 67907bec on 1.x authored by
rahul17 โ
Issue #3434401 by rahul17, patelh84: Automated Drupal 11 compatibility...
-
kuhikar โ
committed 67907bec on 1.x authored by
rahul17 โ
Automatically closed - issue fixed for 2 weeks with no activity.