- Issue created by @project update bot
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
- 🇹🇷Turkey orkut murat yılmaz Istanbul
I assume that it would be better to support D11 with new version.
- 🇧🇪Belgium flyke
There is no release for the issue fork, so can't test a diff file.
Patch from #2 fails to apply on 2.x-dev at this moment. -
kingdutch →
committed 4c87cd92 on 8.x-2.x
Issue #3435792 by Project Update Bot, flyke, melnychukmy, orkut murat...
-
kingdutch →
committed 4c87cd92 on 8.x-2.x
-
kingdutch →
committed 743c401d on 8.x-1.x
Issue #3435792 by Project Update Bot, flyke, melnychukmy, orkut murat...
-
kingdutch →
committed 743c401d on 8.x-1.x
- Status changed to Fixed
7 months ago 8:49pm 26 August 2024 - 🇳🇱Netherlands kingdutch
Tagged 8.x-1.9 → and 8.x-2.0-alpha11 → with Drupal 11 compatibility. Thanks all and thanks thejimberch for pinging me on Slack :)
Automatically closed - issue fixed for 2 weeks with no activity.