- Issue created by @Project Update Bot
- last update
8 months ago 5 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
- last update
8 months ago 5 pass - First commit to issue fork.
- ๐ฎ๐ณIndia chandu7929 Pune
chandu7929 โ changed the visibility of the branch project-update-bot-only to hidden.
- ๐ฎ๐ณIndia chandu7929 Pune
I think we should keep minimum core_version_requirement as
^10.2 || ^11
with respect to changes introduced in 10.2.0 (Refer: https://www.drupal.org/project/drupal/issues/3347291 ๐ Combine field storage and field instance forms Fixed ) and update test accordingly. - ๐ฎ๐ณIndia chandu7929 Pune
Since all tests are passing, hence requesting review.
- Status changed to RTBC
3 months ago 5:27am 20 August 2024 - ๐ฎ๐ณIndia rajeshreeputra Pune
Reviewed MR, tests passing, moving ahead with RTBC.
- ๐ฉ๐ชGermany chr.fritsch ๐ฉ๐ช๐ช๐บ๐
chr.fritsch โ made their first commit to this issueโs fork.
-
chr.fritsch โ
committed 3dc514bc on 8.x-2.x authored by
chandu7929 โ
Issue #3431884: Automated Drupal 11 compatibility fixes for...
-
chr.fritsch โ
committed 3dc514bc on 8.x-2.x authored by
chandu7929 โ
- Status changed to Fixed
2 days ago 2:54pm 13 November 2024 Automatically closed - issue fixed for 2 weeks with no activity.