- Issue created by @project update bot
- Open on Drupal.org โCore: 9.5.x + Environment: PHP 7.4 & 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 (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
9 months ago Waiting for branch to pass - First commit to issue fork.
- ๐ฎ๐ณIndia rajeshreeputra Pune
Rajeshreeputra โ changed the visibility of the branch project-update-bot-only to hidden.
- ๐ฎ๐ณIndia vishalkhode
vishalkhode โ made their first commit to this issueโs fork.
- ๐ฎ๐ณIndia vishalkhode
Thanks @Rajeshreeputra for working on this. The Config Filter โ module dependency has been removed as it's not required.
-
vishalkhode โ
committed dbb72ad0 on 1.x authored by
rajeshreeputra โ
Issue #3434615 by rajeshreeputra, vishalkhode: Automated Drupal 11...
-
vishalkhode โ
committed dbb72ad0 on 1.x authored by
rajeshreeputra โ
- ๐ฎ๐ณIndia vishalkhode
Merged. Hence, closing. Will release shortly. Thanks.
- Status changed to Fixed
3 months ago 6:14pm 19 September 2024 Automatically closed - issue fixed for 2 weeks with no activity.