- Issue created by @project update bot
- last update
about 1 year ago Composer require failure 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-120768This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- last update
about 1 year ago Composer require failure - First commit to issue fork.
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 7.4 & MySQL 5.7last update
11 months ago Waiting for branch to pass -
jcnventura →
committed 10b48d12 on 8.x-1.x authored by
Project Update Bot →
Issue #3428792 by Project Update Bot, jcnventura: Automated Drupal 11...
-
jcnventura →
committed 10b48d12 on 8.x-1.x authored by
Project Update Bot →
- Status changed to Fixed
11 months ago 11:17am 16 May 2024 - 🇵🇹Portugal jcnventura
I'm going to trust the UpdateBot and merge this. It also simplifies the task of testing this with Drupal 11 considerably.
Naturally, this needs to be fully tested before tagging a new release.
Automatically closed - issue fixed for 2 weeks with no activity.