- 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
-
apaderno →
committed 166fab7e on 2.0.x authored by
Project Update Bot →
Issue #3433337: Automated Drupal 11 compatibility fixes
-
apaderno →
committed 166fab7e on 2.0.x authored by
Project Update Bot →
- Status changed to Fixed
9 months ago 12:14pm 25 March 2024 - Status changed to Active
9 months ago 5:30pm 25 March 2024 - 🇧🇪Belgium BramDriesen Belgium 🇧🇪
I think we should keep this one open actually.
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.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
📌 Automated Drupal 11 compatibility fixes for graph_mail Fixed has been created when this issue was still open, which I guess it means that keeping this issue open does not avoid new issues are created.
- Status changed to Fixed
9 months ago 8:47am 26 March 2024 - 🇧🇪Belgium BramDriesen Belgium 🇧🇪
We need to keep one issue open. The duplicate issue being created is a bug in the upgrade bot. I'll re-open the other one
https://www.drupal.org/project/project_analysis/issues/3435972 → Automatically closed - issue fixed for 2 weeks with no activity.