- 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
- First commit to issue fork.
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch 3433700-automated-drupal-11 to hidden.
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch 3433700-automated-drupal-11 to active.
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch project-update-bot-only to active.
- 🇮🇳India vishalkhode
vishalkhode → changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to RTBC
5 months ago 10:50am 24 June 2024 - 🇮🇳India ankitv18
Dropped D8 and pushed a typo fix to pipeline ~~ RTBC+1
- First commit to issue fork.
-
phenaproxima →
committed b57832cb on 8.x-1.x authored by
deepakkm →
Issue #3433700 by deepakkm, phenaproxima, ankitv18: Automated Drupal 11...
-
phenaproxima →
committed b57832cb on 8.x-1.x authored by
deepakkm →
- Status changed to Fixed
5 months ago 2:51pm 10 July 2024 Automatically closed - issue fixed for 2 weeks with no activity.