- 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
- Status changed to RTBC
10 months ago 12:23am 1 July 2024 - 🇦🇺Australia darvanen Sydney, Australia
Looks good to me, no functional code changes, just opens Drupal 11 support.
- Status changed to Needs work
about 1 month ago 9:23am 8 April 2025 - 🇳🇿New Zealand dieuwe Auckland, NZ
There's a hardcoded composer dependency on Drupal 10 that might be good to remove as part of this: https://git.drupalcode.org/project/material_icons/-/blob/2.0.x/composer....
- 🇳🇿New Zealand dieuwe Auckland, NZ
Sorry, I see the proposed merge handles that fine - no actual need to remove the core dependency in
composer.json
although that might still be a good idea since it seems redundant to handle dependencies in two different places.Let's get this merged.
-
b_sharpe →
committed 4605b59a on 2.0.x
Issue #3431829 by dieuwe, darvanen: Automated Drupal 11 compatibility...
-
b_sharpe →
committed 4605b59a on 2.0.x
Automatically closed - issue fixed for 2 weeks with no activity.