- Issue created by @Project Update Bot
- last update
8 months ago Composer error. Unable to continue. 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
- last update
8 months ago Composer error. Unable to continue. - First commit to issue fork.
- 🇮🇳India chandu7929 Pune
chandu7929 → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India chandu7929 Pune
Now I have updated the MR with required change hence requesting review.
- Status changed to RTBC
4 months ago 9:47am 6 August 2024 - First commit to issue fork.
-
mark_fullmer →
committed 86a1eb51 on 2.0.x authored by
chandu7929 →
Issue #3431601: Automated Drupal 11 compatibility fixes for...
-
mark_fullmer →
committed 86a1eb51 on 2.0.x authored by
chandu7929 →
- 🇺🇸United States mark_fullmer Tucson
These changes look great! Excellent implementation for backwards-compatibility with Drupal <10.1. And tests pass on both Drupal 10 and 11. Merging & marking as Fixed! Thanks, everyone!
- Status changed to Fixed
about 2 months ago 8:49pm 7 October 2024 Automatically closed - issue fixed for 2 weeks with no activity.