- 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 → , 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-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
- First commit to issue fork.
- Merge request !11Issue #3434268: Make role expire compatible with Drupal 11 → (Merged) created by rcodina
- 🇪🇸Spain rcodina
rcodina → changed the visibility of the branch project-update-bot-only to hidden.
- 🇪🇸Spain rcodina
With the core 11 update, we are fixing pipeline errors and moving rules integration into a submodule.
-
rcodina →
committed 6773d441 on 4.x
Issue #3434268 by rcodina: Automated Drupal 11 compatibility fixes for...
-
rcodina →
committed 6773d441 on 4.x
- Status changed to Fixed
24 days ago 5:06pm 14 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.