- 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 β 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-115424This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.0
- πΊπΈUnited States luke.leber Pennsylvania
luke.leber β made their first commit to this issueβs fork.
- πΊπΈUnited States luke.leber Pennsylvania
This is NR (for real) now for !4. Green pipelines and adjusted target branch.
@kyle | @brianne | @zach - any chance of a review for this? Thanks.
- πΊπΈUnited States luke.leber Pennsylvania
luke.leber β changed the visibility of the branch project-update-bot-only to hidden.
-
luke.leber β
committed 913c94ae on 2.x
Issue #3428081: Automated Drupal 11 compatibility fixes for...
-
luke.leber β
committed 913c94ae on 2.x
-
luke.leber β
committed 696e3dba on 2.0.x
Issue #3428081: Automated Drupal 11 compatibility fixes for...
-
luke.leber β
committed 696e3dba on 2.0.x
- πΊπΈUnited States luke.leber Pennsylvania
Thanks Kyle.
Merged into 2.x and cherry-picked back to 2.0.x. I'll be cutting 2.0.0 stable shortly and will make 2.0.x the recommended version, but will leave 8.x-1.x supported until the end of Drupal 10 support.
Highly doubtful that this module will see another commit until Drupal 12 though.