- 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-121090This 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.
- Merge request !12Issue #3335775: Take alters from other modules into account when re-using... → (Merged) created by rajeshreeputra
- First commit to issue fork.
- Status changed to RTBC
5 months ago 3:28am 18 July 2024 - 🇮🇳India deepakkm
Changes looks good and pipeline is also green , hence RTBC
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch project-update-bot-only to hidden.
- First commit to issue fork.
- 🇮🇳India ankitv18
RTBC++ Just added minor fixes and now all jobs are green without any warning.
- 🇧🇪Belgium dieterholvoet Brussels
I tested manually and the MR seems enough to make the module work on Drupal 11. RTBC +1
-
DieterHolvoet →
committed 6ccc041e on 8.x-2.x authored by
Rajeshreeputra →
Issue #3430940 by Rajeshreeputra, Project Update Bot, ankitv18, deepakkm...
-
DieterHolvoet →
committed 6ccc041e on 8.x-2.x authored by
Rajeshreeputra →
- Status changed to Fixed
4 months ago 1:21pm 8 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.