- Issue created by @Project Update Bot
- last update
8 months ago 29 pass, 2 fail 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
8 months ago 11:37pm 24 March 2024 - last update
8 months ago 29 pass, 2 fail The last submitted patch, 2: search_api_page.8.x-1.0.rector.patch, failed testing. View results →
- Status changed to Needs review
5 months ago 3:43am 18 June 2024 - Open on Drupal.org →Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7
6:11 6:11 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
- Open on Drupal.org →Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7
5:58 5:58 Queueing - First commit to issue fork.
-
borisson_ →
committed d47b5d48 on 8.x-1.x authored by
Project Update Bot →
Issue #3434389: Automated Drupal 11 compatibility fixes for...
-
borisson_ →
committed d47b5d48 on 8.x-1.x authored by
Project Update Bot →
- Status changed to Fixed
2 months ago 2:27pm 5 September 2024 Automatically closed - issue fixed for 2 weeks with no activity.