- 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-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
- First commit to issue fork.
- Merge request !6Issue #3431622 by DYdave: Added support for Drupal 11. ā (Merged) created by dydave
- š«š·France dydave
dydave ā changed the visibility of the branch project-update-bot-only to hidden.
- First commit to issue fork.
- š§šŖBelgium tim-diels Belgium š§šŖ
Removed the backwards compatibility stuff as thats not needed when adding a version constraint.
Tested this both on 10.x and 11.x and words as expected.
Can we please get this committed?
- š®š¹Italy finex
Hi, this issue is currently blocking me from updating a number of projects. For now, Iām using a fork of the module until an official update is released.
- Status changed to RTBC
3 months ago 1:04pm 23 July 2025 - š§šŖBelgium StryKaizer Belgium
@finex: see https://www.drupal.org/docs/develop/using-composer/using-the-drupal-leni... ā
which allows you to install modules which are not yet updated and apply patches to them.But a release would be nice indeed ;)