- Issue created by @project update bot
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.3 & MySQL 5.7last update
8 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 → 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 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-188138These 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
- Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.3 & MySQL 5.7last update
8 months ago Waiting for branch to pass - 🇨🇦Canada jibran Toronto, Canada
Can we please create a follow-up to fix the test fails?
- 🇨🇦Canada joseph.olstad
The tests ARE passing with Drupal 11.1.
https://git.drupalcode.org/issue/config_revision-3451887/-/jobs/3850135
OK (7 tests, 101 assertions)
Please move forward!
- 🇨🇦Canada joseph.olstad
I also fixed a few phpstan issues and a bunch of phpcs issues.
Intentionally left one remaining phpstan issue (a design choice), accept the risk is my recommendation. Let's move forward please!
-
jibran →
committed 0c08d413 on 1.0.x authored by
project update bot →
Issue #3451887 by joseph.olstad: Drupal 11 compatibility fixes for...
-
jibran →
committed 0c08d413 on 1.0.x authored by
project update bot →
Automatically closed - issue fixed for 2 weeks with no activity.