- 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.
- Merge request !9#3434489 Update core_version_requirement and other Drupal Rector fixes → (Open) created by jamesgrobertson
- Status changed to RTBC
26 days ago 11:52am 7 January 2025 - 🇮🇳India rahul1707
MR !8 changes are working fine with Drupal 10 and Drupal 11. Moving this to RTBC.
- First commit to issue fork.
- 🇺🇸United States AaronBauman Philadelphia
Updated MR 8 from 6.x and included some updates which should have been included in 6.0.0
-
aaronbauman →
committed e555edc3 on 6.x authored by
project update bot →
Issue #3434489 by project update bot, aaronbauman: Automated Drupal 11...
-
aaronbauman →
committed e555edc3 on 6.x authored by
project update bot →
Automatically closed - issue fixed for 2 weeks with no activity.