- Issue created by @project update bot
- last update
about 1 year ago 2 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
- last update
about 1 year ago 2 pass - First commit to issue fork.
- 🇩🇪Germany Grevil
Alright, all done! I dropped the D8 support, fixed remaining D12 deprecation issues and added a ".gitlab-ci.yml", so tests are running again.
Please review!
(Hijacked the bot branch, since there are no more automatic commits anyway.)
- Status changed to RTBC
5 months ago 8:35am 21 November 2024 - 🇩🇪Germany Anybody Porta Westfalica
Perfect, thank you @grevil! Could you maybe contact @geekmerlin to merge this and tag a D11 compatible release? Would be great!
-
geek-merlin →
committed 6db04182 on 8.x-1.x authored by
project update bot →
Issue #3435285: Automated Drupal 11 compatibility fixes for...
-
geek-merlin →
committed 6db04182 on 8.x-1.x authored by
project update bot →
- 🇩🇪Germany Anybody Porta Westfalica
Thank you @geek-merlin that was our last D11 blocker 🎉
Automatically closed - issue fixed for 2 weeks with no activity.