- 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 (MR) 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 or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- First commit to issue fork.
-
Anybody →
committed fb9047ff on 8.x-1.x authored by
Project Update Bot →
Issue #3435456: Automated Drupal 11 compatibility fixes for...
-
Anybody →
committed fb9047ff on 8.x-1.x authored by
Project Update Bot →
- Status changed to RTBC
9 months ago 7:06am 25 March 2024 - Status changed to Fixed
5 months ago 10:44am 9 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India Vivek Panicker Kolkata
Hi @anybody, I see the issue has been marked fixed but we don't have a D11 release yet.
Is there any plan to launch a D11 version soon?
We were working on updating our site to D11 and found that this module is not yet compatible. - 🇩🇪Germany Anybody Porta Westfalica
Thanks @vivek panicker you're right, sorry! Tagged a new release!
- 🇮🇳India Vivek Panicker Kolkata
Thanks a lot for the quick action @anybody!
Very much appreciated! :)