- Issue created by @Project Update Bot
- last update
8 months ago 8 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 β 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, 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
8 months ago 8 fail The last submitted patch, 2: juicebox.4.0.0-alpha1.rector.patch, failed testing. View results β
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- πΊπΈUnited States fkelly
Please disregard #5 through #12. These were created automatically (somehow) as soon as I came in to look at #2. I can't find anyway to delete issue #'s once they are created. Which I realize may be intentional on Drupal.org's part but really all I did was sign in via Lastpass can go in to look at #2. The watchdog patches should be taken care in patches for Drupal 10 that I have pending.
- πΊπΈUnited States fkelly
I am closing this until we have a stable version to test the suggested changes against. Version 4.0.0-alpha does not include changes made after that code. These are numerous. We need at least another alpha, beta or even a stable release before using Drupal rector changes against that. No point spinning Drupal rector wheels on a dead end street.
- Status changed to Closed: won't fix
8 months ago 8:43pm 21 March 2024