- 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
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.2, 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-188815These 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
- First commit to issue fork.
- 🇮🇳India rajeshreeputra Pune
With the changes from 🐛 Error on Drupal 10.3.0-beta1 because some core CSS libraries moved Needs work created MR !5.
- 🇮🇳India rajeshreeputra Pune
Rajeshreeputra → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India ankitv18
Can we support minimum drupal version 9.5 instead of 9? (If not in plan to drop D9 completely.)
-
Rajeshreeputra →
committed 6f9d001c on 2.0.x
Issue #3434747: Automated Drupal 11 compatibility fixes for stable
-
Rajeshreeputra →
committed 6f9d001c on 2.0.x
- 🇮🇳India rajeshreeputra Pune
Released 2.0.1 with off-canvas and GitLab CI change. Create !MR6 for Drupal 10.3 and 11 readiness.
- Status changed to RTBC
4 months ago 7:21am 17 July 2024 -
Rajeshreeputra →
committed 39c918a8 on 2.x
Issue #3434747 by Rajeshreeputra, chandu7929, ankitv18, vishalkhode:...
-
Rajeshreeputra →
committed 39c918a8 on 2.x
- Status changed to Fixed
4 months ago 7:47am 17 July 2024 Automatically closed - issue fixed for 2 weeks with no activity.