- 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
- Status changed to Postponed
5 months ago 10:11am 21 November 2024 - π§πͺBelgium dieterholvoet Brussels
Postponed until Flysystem is compatible with Drupal 11.
- π©πͺGermany skrug Bamberg
Hi, Flysystem in version 2.3.0-alpha2 is now Drupal 11 compatible.
- π§πͺBelgium dieterholvoet Brussels
@skrug did you test the MR? Does the module work with the new versions of Flysystem and Drupal? I don't use this module anymore myself, but I'll be happy to merge the MR and create a release once it has been tested.
- π§πͺBelgium dieterholvoet Brussels
dieterholvoet β changed the visibility of the branch fix-composer-json to hidden.
- π§πͺBelgium dieterholvoet Brussels
dieterholvoet β changed the visibility of the branch 3430646-automated-drupal-11 to hidden.
-
dieterholvoet β
committed 83f2e570 on 8.x-1.x authored by
project update bot β
Issue #3430646 by project update bot, dieterholvoet, joecorall:...
-
dieterholvoet β
committed 83f2e570 on 8.x-1.x authored by
project update bot β
- Status changed to Fixed
1 day ago 8:59am 1 May 2025 Automatically closed - issue fixed for 2 weeks with no activity.