- 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 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-120024This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.
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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- Status changed to Closed: works as designed
8 months ago 7:52am 2 May 2024 - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
This is causing tests to fail on Drupal 9:
Error: Undefined constant Symfony\Component\HttpKernel\HttpKernelInterface::MAIN_REQUEST
— https://git.drupalcode.org/issue/cdn-3428342/-/jobs/1238866
That actually nicely demonstrates that the
4.x
branch cannot be compatible with Drupal 9+10+11, and that we hence need a new branch to support Drupal 10+11.That's also visible in HEAD of this module being tested against Drupal 11, where the inverse complaint about a missing constant exists:
Error: Undefined constant Symfony\Component\HttpKernel\HttpKernelInterface::MASTER_REQUEST
— https://git.drupalcode.org/project/cdn/-/jobs/1492770
The one constant is available only in Drupal 9+10, the other only in 10+11.
See 🌱 5.x requiring PHP 8.2 and >=10.2, 6.x requiring PHP 8.3 and >=11? Or skip that 5.x? Active for the plan for
5.x
.