- 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 (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
10 months ago 3:29am 18 June 2024 - First commit to issue fork.
- 🇺🇸United States BenStallings
With the addition of a composer.json file, MR!5 now installs & can be enabled in Drupal 11. Somebody please confirm. Thanks!
- 🇧🇪Belgium dieterholvoet Brussels
dieterholvoet → changed the visibility of the branch project-update-bot-only to hidden.
- 🇧🇪Belgium dieterholvoet Brussels
dieterholvoet → changed the visibility of the branch 3455293-automated-drupal-11 to hidden.
- 🇧🇪Belgium dieterholvoet Brussels
No need to add a
composer.json
file unless there are dependencies that can't be defined in theinfo.yml
file. I deleted it again -
dieterholvoet →
committed 2f270896 on 8.x-1.x authored by
benstallings →
Issue #3455293 by project update bot, benstallings, dieterholvoet:...
-
dieterholvoet →
committed 2f270896 on 8.x-1.x authored by
benstallings →
Automatically closed - issue fixed for 2 weeks with no activity.