- 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
- 🇬🇷Greece gbotis
I have tested the module with the requirements change and did not find any issues. Are there any plans for a deploy?
- Status changed to RTBC
4 months ago 1:59pm 13 March 2025 - 🇬🇧United Kingdom andy_w
We have also been utilising this really useful module on drupal 11 with the above patch without issue, and it would be great to see a release.
- First commit to issue fork.
-
mmenavas →
committed 51e932e1 on 3.x authored by
project update bot →
Issue #3429216 by project update bot: Automated Drupal 11 compatibility...
-
mmenavas →
committed 51e932e1 on 3.x authored by
project update bot →
- 🇺🇸United States mmenavas
I also confirm that updating the core version requirement is all that is needed to make a D11 compatible release.
Automatically closed - issue fixed for 2 weeks with no activity.