- Issue created by @project update bot
- last update
10 months ago 4 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
10 months ago 4 pass - Status changed to RTBC
2 months ago 9:52pm 25 November 2024 - 🇧🇬Bulgaria pfrenssen Sofia
Looks good, code is already Drupal 11 compatible, only the info file needs to be updated.
- 🇮🇳India sheshsharma
MR!13 Makes this module compatible with Drupal 11. Functionality is working as expected.
RTBC +1 -
damienmckenna →
committed 7c3f3da2 on 8.x-3.x authored by
project update bot →
#3434906 by project update bot, sheshsharma, pfrenssen, damienmckenna:...
-
damienmckenna →
committed 7c3f3da2 on 8.x-3.x authored by
project update bot →
- 🇯🇴Jordan Rajab Natshah Jordan
Thanks, Damien, for merging!
Hoping for a tag release soon to help speed up real physical testing in projects. - Status changed to Fixed
2 days ago 5:03pm 25 January 2025 - 🇧🇪Belgium bart lambert
I am also hoping for a tagged release if you’ve got some free time. Appreciate it!