- Issue created by @project update bot
- last update
10 months ago 267 pass, 4 fail 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
- last update
10 months ago 267 pass, 4 fail The last submitted patch, 2: migmag.1.8.1.rector.patch, failed testing. View results β
- Status changed to Needs review
7 months ago 2:14am 18 June 2024 - Open on Drupal.org βCore: 9.5.x + Environment: PHP 8.0 & MySQL 5.7
43:50 43:50 Queueing 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.0 & MySQL 5.7
43:37 43:37 Queueing - Status changed to Postponed
7 months ago 10:05am 29 June 2024 - ππΊHungary huzooka Hungary ππΊπͺπΊ
Adding related issues which are blocking this to happen: π Automated Drupal 11 compatibility fixes for eme Needs review and π Automated Drupal 11 compatibility fixes for smart_sql_idmap Needs review .
- ππΊHungary huzooka Hungary ππΊπͺπΊ
Also this: π Create a release compatible with Drupal 11 Fixed
- Assigned to huzooka
- Status changed to Needs work
7 months ago 11:13am 30 June 2024 - ππΊHungary huzooka Hungary ππΊπͺπΊ
Blockers are addressed, ready for work.
- ππΊHungary huzooka Hungary ππΊπͺπΊ
huzooka β changed the visibility of the branch 3433398-automated-drupal-11 to hidden.
- ππΊHungary huzooka Hungary ππΊπͺπΊ
huzooka β changed the visibility of the branch project-update-bot-only to hidden.
-
huzooka β
committed 294170ca on 1.8.x
Issue #3433398 by huzooka: Drupal 11 compatibility fixes for migmag
-
huzooka β
committed 294170ca on 1.8.x
- ππΊHungary huzooka Hungary ππΊπͺπΊ
Tests are green, going to merge and create a new release soonish.
I had to remove color and suppress tests using it because drupal/color has no Drupal11 compatible release yet. Added π Re-enable testing of RollbackableColor plugin Active to not forget about restoring these temporary changes. Automatically closed - issue fixed for 2 weeks with no activity.