- 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 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, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-120835This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- First commit to issue fork.
- 🇮🇳India manishvaity mumbai
MR!5 Makes this module compatible with Drupal 11. Functionality is working as expected.
- 🇮🇳India sheshsharma
MR!5 Makes this module compatible with Drupal 11. Functionality is working as expected.
RTBC +1 - Status changed to RTBC
about 2 months ago 1:21pm 20 March 2025 - 🇫🇷France Anwoon
MR!5 Makes this module compatible with Drupal 11. Functionality is working as expected.
- 🇺🇸United States bkosborne New Jersey, USA
rector bot posted a patch adding compatibility, I don't understand why the MR was needed? I'm going to commit that original patch. For adding Gitlab CI support, please add a separate issue. Thank you all.
-
bkosborne →
committed 70457881 on 3.0.x
Issue #3429203 by project update bot: Automated Drupal 11 compatibility...
-
bkosborne →
committed 70457881 on 3.0.x
Automatically closed - issue fixed for 2 weeks with no activity.