- Issue created by @project update bot
30:10 27:56 RunningThis 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 → , 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.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- Status changed to Needs review
over 1 year ago 7:33pm 4 April 2024 29:55 27:56 Running- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8
0:02 0:02 Queueing 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.3, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
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-199781These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Open on Drupal.org →Core: 10.2.x + Environment: PHP 8.2 & MySQL 8
59:48 59:48 Queueing - a1f5adb3 committed on 6.0.x
Issue #3438563 by Nathaniel: Drupal 11 compatibility fixes.
- a1f5adb3 committed on 6.0.x
- ef2135fd committed on 6.0.x
Issue #3438563 by Nathaniel: Continue working on Drupal 11 compatibility...
- ef2135fd committed on 6.0.x
- 0b93d997 committed on 6.0.x
Issue #3438563 by Nathaniel: Continue working on tests and deprecated...
- 0b93d997 committed on 6.0.x
- 48372a87 committed on 6.0.x
Issue #3438563 by Nathaniel: Revert ContentEntityType attribute...
- 48372a87 committed on 6.0.x