- 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
- πΊπ¦Ukraine eugene.brit Kyiv πΊπ¦
eugene.brit β made their first commit to this issueβs fork.
Confirmed. Please merge MR !9 rather than 7. MR 9 adds composer.json to the project.
- Assigned to mkalkbrenner
- Status changed to RTBC
3 months ago 8:04am 19 May 2025 - πΊπΈUnited States hargobind Austin, Texas
Assigning to @mkalkbrenner who manages the D9+ branches.
Raising priority to Major since this is a relatively simple fix to enable D11 compatibility.
-
mkalkbrenner β
committed c217ac90 on 3.0.x authored by
eugene.brit β
Resolve #3435434 "Automated drupal 11"
-
mkalkbrenner β
committed c217ac90 on 3.0.x authored by
eugene.brit β
@mkalkbrenner Thanks for that! Can we have a new release as well?
Automatically closed - issue fixed for 2 weeks with no activity.