- 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 โ , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.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
- @project-update-bot opened merge request.
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-185727These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
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-188138These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- ๐บ๐ธUnited States emptyvoid
Updated with code changes based on update status automated code review.
- First commit to issue fork.
- @pbonnefoi opened merge request.
- ๐ช๐ธSpain psf_ Huelva
Hi, the patch require update composer.json too, I think :)
- ๐ฌ๐งUnited Kingdom darren.fisher
darren.fisher โ made their first commit to this issueโs fork.
- ๐ฌ๐งUnited Kingdom darren.fisher
All green and good to go I think. Can we get this reviewed ASAP as this is the last module holding up one of site upgrades to Drupal 11!
All green pipeline:
https://git.drupalcode.org/issue/entity_update-3430260/-/pipelines/439664Patch for those using composer lenient:
https://git.drupalcode.org/project/entity_update/-/merge_requests/12.diff - ๐ซ๐ทFrance pbonnefoi
Sounds good to me, good job. Hope a maintainer will merge this anytime soon.
- ๐ฎ๐ณIndia sivakarthik229
Thanks for the D11 compatability fixes of the module.
- 6c146488 committed on 3.0.x
Issue #3430260 by project update bot, emptyvoid, pbonnefoi: Automated...
- 6c146488 committed on 3.0.x