- 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.
- Status changed to Needs work
6 months ago 6:00am 27 June 2024 - First commit to issue fork.
- 🇮🇳India ankitv18
ankitv18 → changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to Needs review
4 months ago 9:57am 22 August 2024 - 🇺🇦Ukraine SmovS Lutsk
I have tested and confirm that MR!7 is working.
Test environment:
Drupal 11.0.4
PHP 8.3.10I used Drupal's Lenient Composer Endpoint to install "drupal/field_group_table:^1.1" on Drupal 11.
After that, I installed and applied MR!7 as a patch with dependencies and enabled the module via Drush.
Also, I tested the usage workflow via UI and it worked as expected.There were no issues or errors during that.
- 894ad545 committed on 8.x-1.x
Issue #3430507 by project update bot, vladimiraus, ankitv18, smovs:...
- 894ad545 committed on 8.x-1.x
- Status changed to Fixed
about 1 month ago 1:11pm 12 November 2024 Automatically closed - issue fixed for 2 weeks with no activity.