- Issue created by @project update bot
- last update
11 months ago 2 pass 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
- last update
11 months ago 2 pass - Status changed to RTBC
2 months ago 2:32pm 28 November 2024 - 🇮🇳India shashi_shekhar_18oct
MR!4 Makes this module compatible with Drupal 11. Functionality is working as expected.
RTBC +1
- 🇮🇳India abhi_khandelwal Gandhinagar
The #MR4 works for both Drupal 10 and Drupal 11. Attaching the upgrade status screenshot for reference.
- 🇨🇭Switzerland berdir Switzerland
I explained in 🌱 Offer to co-maintain entityform_block Needs review what I expect this issue to do, namely add gitlab CI configuration so we have passing tests on Drupal 10 and 11.
-
berdir →
committed aba98ad0 on 8.x-1.x authored by
project update bot →
Issue #3430273 by project update bot, joseph.olstad, berdir: Automated...
-
berdir →
committed aba98ad0 on 8.x-1.x authored by
project update bot →
- 🇨🇦Canada joseph.olstad
@berdir, friendly reminder to please tag 1.0-alpha5
Automatically closed - issue fixed for 2 weeks with no activity.