- Issue created by @Project Update Bot
- Open on Drupal.org βCore: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
2:09 2:09 Queueing 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 β , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.3, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
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-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Status changed to Needs review
3 months ago 2:06am 18 June 2024 - Open on Drupal.org βCore: 9.5.x + Environment: PHP 8.1 & MySQL 5.7
1:42 1:42 Queueing - First commit to issue fork.
-
phenaproxima β
committed ef84641a on 1.0.x authored by
Project Update Bot β
Issue #3455258: Automated Drupal 11 compatibility fixes for...
-
phenaproxima β
committed ef84641a on 1.0.x authored by
Project Update Bot β
- Status changed to Fixed
about 2 months ago 12:25pm 22 July 2024 Automatically closed - issue fixed for 2 weeks with no activity.