- Issue created by @project update bot
- last update
9 months 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 (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
- last update
9 months ago Composer require failure - Open on Drupal.org →Core: 10.2.1 + Environment: PHP 7.4 & MySQL 5.7last update
6 months ago Not currently mergeable. - last update
6 months ago Composer require failure - First commit to issue fork.
- last update
6 months ago Composer require failure - last update
6 months ago Composer require failure - last update
6 months ago Composer require failure - 🇮🇳India ankitv18
Will remove the forked repo of schemata once its get merged.
Validated the functionality it is working fine with the current MR. - 🇮🇳India ankitv18
ankitv18 → changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to RTBC
5 months ago 4:47am 24 July 2024 - 🇺🇸United States bradjones1 Digital Nomad Life
Thanks for referring this over to me for review.
-
bradjones1 →
committed ee6302c5 on 3.x authored by
ankitv18 →
Issue #3433698 by ankitv18, bradjones1: Automated Drupal 11...
-
bradjones1 →
committed ee6302c5 on 3.x authored by
ankitv18 →
- Status changed to Fixed
5 months ago 5:54pm 2 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.