- Issue created by @Project Update Bot
- last update
8 months ago Composer require-dev failure 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 → these changes make this module compatible with Drupal 11! 🎉
Therefore these changes update theinfo.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 require-dev failure - First commit to issue fork.
- last update
8 months ago Composer require-dev failure - last update
8 months ago Composer require-dev failure -
eiriksm →
committed 3465fe03 on 8.x-1.x authored by
Project Update Bot →
Issue #3429657 by Project Update Bot, eiriksm: Automated Drupal 11...
-
eiriksm →
committed 3465fe03 on 8.x-1.x authored by
Project Update Bot →
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 8.1 & MySQL 8last update
5 months ago Waiting for branch to pass 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: 9.5.x + Environment: PHP 8.1 & MySQL 8last update
5 months ago Waiting for branch to pass - Open on Drupal.org →Core: 9.5.x + Environment: PHP 8.1 & MySQL 8last update
5 months ago Waiting for branch to pass -
eiriksm →
committed b2518814 on 8.x-1.x authored by
Project Update Bot →
Issue #3429657: Automated Drupal 11 compatibility fixes for...
-
eiriksm →
committed b2518814 on 8.x-1.x authored by
Project Update Bot →
- Status changed to Active
5 months ago 7:47pm 19 June 2024