- 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
- Status changed to Needs review
9 months ago 1:33am 25 March 2024 - Status changed to RTBC
5 months ago 1:14pm 8 July 2024 - πΊπ¦Ukraine paulrad
Can confirm that the changes works fine with the Drupal 11 and current 8.x-4.x-dev branch. Moving to the RTBC
- πΊπ¦Ukraine voleger Ukraine, Rivne
voleger β changed the visibility of the branch 3434755-automated-drupal-11 to hidden.
- πΊπ¦Ukraine voleger Ukraine, Rivne
voleger β changed the visibility of the branch 3434755-automated-drupal-11 to active.
-
voleger β
committed 60fbe25e on 8.x-4.x authored by
Project Update Bot β
Issue #3434755 by Project Update Bot, voleger, paulrad: Automated Drupal...
-
voleger β
committed 60fbe25e on 8.x-4.x authored by
Project Update Bot β
Automatically closed - issue fixed for 2 weeks with no activity.