- Issue created by @project update bot
- last update
10 months ago 40 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 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.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- last update
10 months ago 40 pass, 2 fail The last submitted patch, 2: dubbot.1.0.0.rector.patch, failed testing. View results →
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
7 months ago Waiting for branch to 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.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
7 months ago 11:55pm 17 June 2024 - Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 8last update
7 months ago Waiting for branch to pass - First commit to issue fork.
- 🇺🇸United States markie Albuquerque, NM
Found a small issue with a change in the configFormBase constructor that doesn't seem to be picked up. Tested in DrupalPod successfully but since Dubbot isn't looking for the test instance that is as far as I can get without releasing this. Can someone please review the MR and mark RTBS before I commit?
- 🇺🇸United States davidburns Philadelphia
Code reviewed and approved.
Tested on Tugboat. -
markie →
committed d46519ab on 1.0.x authored by
project update bot →
Issue #3429983 by markie, davidburns: Automated Drupal 11 compatibility...
-
markie →
committed d46519ab on 1.0.x authored by
project update bot →
- 🇺🇸United States markie Albuquerque, NM
MR has been merged and ready for a D11 release. Thanks for your contribution.