- Issue created by @project update bot
- last update
about 1 year ago 3 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
- Merge request !6Issue #3431872: Drupal 11 compatibility fixes. → (Merged) created by project update bot
- last update
about 1 year ago 3 pass - 🇩🇪Germany Grevil
Added a few more changes rector didn't catch. Note that minimum version requirement needs to be "10.3" now, as "renderInIsolation" didn't exist prior.
- 🇩🇪Germany Anybody Porta Westfalica
LGTM, but the maintainers should please have a look and test. RTBC+1
- Assigned to joevagyok
- 🇩🇪Germany Grevil
The validation didn't work at all! Should have tested it better, my apologies. The deprecation error was a bit misleading and I didn't fully read on the change record.
Should be all green now!
- Status changed to Fixed
8 months ago 10:24am 21 August 2024 -
joevagyok →
committed 4835b8d7 on 8.x-1.x authored by
Project Update Bot →
Issue #3431872: Drupal 11 compatibility fixes.
-
joevagyok →
committed 4835b8d7 on 8.x-1.x authored by
Project Update Bot →
Automatically closed - issue fixed for 2 weeks with no activity.