- Issue created by @project update bot
- Open in Jenkins โ Open on Drupal.org โCore: 10.2.1 + Environment: PHP 8.0 & MySQL 5.7 updated depslast update
9 months ago Composer require failure 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
- Open in Jenkins โ Open on Drupal.org โCore: 10.2.1 + Environment: PHP 8.0 & MySQL 5.7 updated depslast update
9 months ago Composer require failure -
kim.pepper โ
committed bc948bba on 8.x-1.x
Issue #3433678: Automated Drupal 11 compatibility fixes for...
-
kim.pepper โ
committed bc948bba on 8.x-1.x
- First commit to issue fork.
- ๐ฆ๐บAustralia kim.pepper ๐โโ๏ธ๐ฆ๐บSydney, Australia
kim.pepper โ made their first commit to this issueโs fork.
- ๐ฎ๐ณIndia ankitv18
ankitv18 โ changed the visibility of the branch project-update-bot-only to hidden.
-
kim.pepper โ
committed fb54cfed on 8.x-1.x authored by
ankitv18 โ
Issue #3433678 by kim.pepper, ankitv18: Automated Drupal 11...
-
kim.pepper โ
committed fb54cfed on 8.x-1.x authored by
ankitv18 โ
- Status changed to Fixed
5 months ago 9:43pm 5 August 2024 - ๐ฆ๐บAustralia kim.pepper ๐โโ๏ธ๐ฆ๐บSydney, Australia
Committed to 8.x-1.x. Thanks!
Automatically closed - issue fixed for 2 weeks with no activity.