- 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-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 Active
6 months ago 1:42am 8 September 2024 - Status changed to Needs work
about 1 month ago 12:23pm 31 January 2025 - 🇬🇧United Kingdom scott_euser
Test failure for D11:
1) Drupal\Tests\config_views\Functional\DefaultViewsTest::testViews Drupal\Core\Extension\Exception\UnknownExtensionException: Unknown themes: classy.
- 🇬🇧United Kingdom scott_euser
scott_euser → changed the visibility of the branch project-update-bot-only to hidden.
- 🇬🇧United Kingdom scott_euser
Okay tests now pass with this (but I've had to take the code from 🐛 Dynamic property issue in ConfigEntityQuery with PHP 8.2 RTBC for tests to pass otherwise the deprecation is a fatal error in php 8.3).
- 🇬🇧United Kingdom scott_euser
Added 🐛 Fix phpcs, phpstan, cspell Postponed for after this is merged (set it to postponed for now)
-
scott_euser →
committed 8a24e52a on 2.0.x authored by
dqd →
Issue #3429482 by dqd, scott_euser: Automated Drupal 11 compatibility...
-
scott_euser →
committed 8a24e52a on 2.0.x authored by
dqd →
Automatically closed - issue fixed for 2 weeks with no activity.