- Issue created by @project update bot
- last update
9 months ago Patch Failed to Apply 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 on Drupal.org βCore: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
9 months ago Not currently mergeable. - last update
7 months ago 2 pass 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.1, 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-177898These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
7 months ago 2 pass - last update
7 months ago CI error 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-185727These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
7 months ago CI error - Status changed to RTBC
3 months ago 12:13pm 4 October 2024 - Status changed to Needs work
19 days ago 3:55am 4 December 2024 - πΊπΈUnited States markdorison
Tests are not currently passing or able to run and the MR is showing as unmergeable.
- ivnish Kazakhstan
ivnish β changed the visibility of the branch 3435793-automated-drupal-11 to hidden.
- ivnish Kazakhstan
@markdorison I fixed test. MR looks mergeable, please review
- πΊπΈUnited States markdorison
@ivnish This looks great; thank you!
Since this is dropping support for Drupal 9, does anyone feel that we should create a new major version of the module or are we so far past when Drupal 9 support was dropped (11/1/23) that we should not worry about that?