- Issue created by @project update bot
- last update
9 months ago 71 pass, 16 fail 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
9 months ago 71 pass, 16 fail - Status changed to Needs work
9 months ago 12:22pm 21 March 2024 - 🇺🇸United States danflanagan8 St. Louis, US
There are a lot of test failures like:
1) Drupal\Tests\crossword\Functional\CrosswordImageRegenerateTest::testRegenerate
Error: Call to undefined method Drupal\system\Plugin\ImageToolkit\GDToolkit::setImage()Haven't investigate what API changes have resulted in that, but it looks like there's something important that is changing in D11. Hoepfully upcoming patches with fix that.
- Status changed to Needs review
9 months ago 2:54pm 4 April 2024 - last update
9 months ago 71 pass, 16 fail This comment was forced and has ignored the check if a change was already posted. This is only done when we want to update the issue without waiting for changes to happen.
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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- last update
9 months ago 71 pass, 16 fail - last update
8 months ago 71 pass, 16 fail -
danflanagan8 →
committed 8236f3b0 on 2.0.x authored by
Project Update Bot →
Issue #3429677: Automated Drupal 11 compatibility fixes for crossword
-
danflanagan8 →
committed 8236f3b0 on 2.0.x authored 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.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-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
- Merge request !1Automated Project Update Bot fixes from run 11-188138. → (Merged) created by danflanagan8
-
danflanagan8 →
committed af56ac79 on 2.0.x
Issue #3429677: Automated Drupal 11 compatibility fixes for crossword
-
danflanagan8 →
committed af56ac79 on 2.0.x
- Status changed to Active
7 months ago 8:48pm 6 June 2024 - Status changed to Needs review
6 months ago 11:30pm 17 June 2024 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
-
danflanagan8 →
committed 5b98a5bc on 2.0.x authored by
Project Update Bot →
Issue #3429677 by danflanagan8: Automated Drupal 11 compatibility fixes...
-
danflanagan8 →
committed 5b98a5bc on 2.0.x authored by
Project Update Bot →
- Status changed to Fixed
4 months ago 9:01pm 27 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.