- Issue created by @project update bot
- last update
10 months ago 198 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
- last update
10 months ago 198 pass - First commit to issue fork.
- πΊπΈUnited States jrglasgow Idaho
according to my testing it appears to be working
- π¬π§United Kingdom scott_euser
Adding related issue in AI module that depends on this
- π¬π§United Kingdom scott_euser
scott_euser β changed the visibility of the branch project-update-bot-only to hidden.
- π¬π§United Kingdom scott_euser
- Hiding unused branches and patches to make it easier for maintainers
- Also see β¨ Drupal 11 compatibility Needs review would be good to know which issue is the correct one
- πΊπΈUnited States markie Albuquerque, NM
I would recommend supporting this issue over the other one.
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
- πͺπΈSpain enchufe Spain
Added missing core requirement to legacy module for
3.0.x
rerroll. - πΊπΈUnited States BenStallings
I made @enchufe's patch into a merge request and can verify that MR!12 can be installed and enabled in Drupal 11.
- Status changed to Fixed
4 months ago 8:09am 27 November 2024 Automatically closed - issue fixed for 2 weeks with no activity.