- 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
- ๐ฎ๐ณIndia samit.310@gmail.com
samit.310@gmail.com โ made their first commit to this issueโs fork.
- ๐ฎ๐ณIndia samit.310@gmail.com
samit.310@gmail.com โ changed the visibility of the branch project-update-bot-only to hidden.
- ๐ฎ๐ณIndia samit.310@gmail.com
We should use a new Git Branch for Drupal 10.2 and 11, As
TypedConfigManagerInterface $typed_config_manager
changes related toConfigFormBase
are introduced in 10.2.Thanks
Samit K. - Status changed to Fixed
6 months ago 8:33am 13 August 2024 - ๐ช๐ธSpain rodrigoaguilera Barcelona
Thanks for the contribution.
Why a new branch? The future 1.7 version can drop support for Drupal < 10.2.
Do you think is ready for release?
- ๐ฎ๐ณIndia samit.310@gmail.com
Hi @rodrigoaguilera,
if 1.7 version is dropping support for Drupal < 10.2, this will also works.
+1 for ready for release.
Thanks
Samit K. Automatically closed - issue fixed for 2 weeks with no activity.
- ๐ช๐ธSpain rodrigoaguilera Barcelona
Thanks for the reminder.
I just tagged an new version