- 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 → 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 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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Status changed to RTBC
5 months ago 10:26am 9 August 2024 - Status changed to Fixed
5 months ago 10:28am 9 August 2024 -
Anybody →
committed 31883d7f on 4.x authored by
Project Update Bot →
Issue #3434242 by Project Update Bot, Anybody: Automated Drupal 11...
-
Anybody →
committed 31883d7f on 4.x authored by
Project Update Bot →
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇺🇸United States smustgrave
Possible to get a tagged release of this module please.
- 🇩🇪Germany Anybody Porta Westfalica
@smustgrave tests are currently failing and I don't have time to fix that currently. If you can confirm 4.x is fine for a stable release or fix the tests, I can of course tag a new beta2 release compatible with Drupal 11. Just don't want to break something in a rush. Thanks!