- Issue created by @Project Update Bot
- last update
7 months ago 7 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-120835This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- Status changed to RTBC
4 months ago 12:45pm 20 May 2024 - Status changed to Needs work
4 months ago 9:01pm 5 June 2024 - 🇨ðŸ‡Switzerland berdir Switzerland
A merge request with a .gitlab-ci.yml that tests previous/next minor/major is necessary to verify this works and tests pass.
- last update
4 months ago 7 pass - last update
4 months ago 2 pass, 4 fail -
Berdir →
committed b5b5b2e4 on 8.x-1.x
Issue #3429007: Automated Drupal 11 compatibility fixes for block_field
-
Berdir →
committed b5b5b2e4 on 8.x-1.x
- Status changed to Fixed
4 months ago 10:18pm 10 June 2024 - 🇨ðŸ‡Switzerland berdir Switzerland
Needed some workarounds for config schema changes in 10.3 and add another submit changes in 10.2, now all tests are passing from previous major to next major, merged.
Automatically closed - issue fixed for 2 weeks with no activity.