- 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-185727These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- Status changed to Needs review
6 months ago 7:36pm 30 May 2024 - First commit to issue fork.
- 🇩🇪Germany SteffenR Germany
Just a quick note.
Due to dependency on tmgmt, we cannot merge this MR, because tmgmt still has missing dependencies/ is not compatible with Drupal 11.
- Status changed to Postponed
5 months ago 7:50am 6 June 2024 - Assigned to SteffenR
- Status changed to Active
about 2 months ago 8:01am 1 October 2024 - 🇩🇪Germany SteffenR Germany
steffenr → changed the visibility of the branch project-update-bot-only to hidden.
- 🇩🇪Germany SteffenR Germany
steffenr → changed the visibility of the branch 3451351-automated-drupal-11 to hidden.
- 🇩🇪Germany SteffenR Germany
I've added a new MR fixing the issues, since the MR provided by the bot was missing some additions made to the module.
-
steffenr →
committed 1b410f2f on 2.2.x
#3451351: add Drupal 11 compatibility
-
steffenr →
committed 1b410f2f on 2.2.x
-
steffenr →
committed 1b410f2f on 2.3.x
#3451351: add Drupal 11 compatibility
-
steffenr →
committed 1b410f2f on 2.3.x
Automatically closed - issue fixed for 2 weeks with no activity.