- Issue created by @Project Update Bot
3:49 0:30 RunningThis 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
3:38 58:30 Running- last update
8 months ago Composer require failure This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.
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.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
- last update
8 months ago Composer require failure -
RobLoach →
committed 3be34f4d on 2.0.x
Issue #3429894: Fix return type of NewCommentSubscriber
-
RobLoach →
committed 3be34f4d on 2.0.x
- Status changed to Fixed
6 months ago 7:37pm 30 May 2024 - 🇬🇧United Kingdom steven jones
@RobLoach you might want to leave this issue open, so that this module continues to get updates from the @Project Update Bot ?
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇺🇸United States sikofitt
This is still not compatible with 11. Is it possible to bump the version and push out a new release?
core_version_requirement: ^9 || ^10
- 🇺🇦Ukraine Ruslan Piskarov Kiev, Ukraine
+1 for an official Drupal 11 release.
Thanks for working on this!