- 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 → , 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-318179These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.6
- mglaman/phpstan-drupal: 1.3.1
- palantirnet/drupal-rector: 0.20.3
The reason why patch #2 is needed
In Drupal 11 PHPUnit has been upgraded from 9.5 to 10.5. And in PHPUnit 10 @dataProvider methods must be static.
References
1. https://www.drupal.org/project/drupal/releases/11.0.0 →
2. https://www.drupal.org/node/3365413 →Tasks
1. In 1.0.x branch remove Drupal 11 support (core_version_requirement: ^10.2) and create a new release.
2. Create a new 2.0.x branch for Drupal 11 version (core_version_requirement: ^11), make changes, test it and create a new 2.0.1 release.-
wombatbuddy →
committed 051a2128 on 1.0.x
Issue #3482954: Mark the branch as not compatible with Drupal 11
-
wombatbuddy →
committed 051a2128 on 1.0.x