- Issue created by @project update bot
- last update
8 months ago PHPLint Failed 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
8 months ago PHPLint Failed - last update
8 months ago PHPLint Failed 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
8 months ago PHPLint Failed - First commit to issue fork.
- last update
6 months ago PHPLint Failed - last update
6 months ago PHPLint Failed - last update
6 months ago PHPLint Failed - last update
6 months ago PHPLint Failed - last update
6 months ago PHPLint Failed - last update
6 months ago PHPLint Failed - last update
6 months ago PHPLint Failed - last update
6 months ago PHPLint Failed - last update
6 months ago 55 pass - last update
6 months ago 55 pass - last update
6 months ago 55 pass - 🇮🇳India vishalkhode
vishalkhode → changed the visibility of the branch project-update-bot-only to hidden.
- last update
6 months ago run-tests.sh fatal error - 🇮🇳India vishalkhode
@Rajeshreeputra: The PHPUnit tests were failing on Drupal 11. See this. I've pushed the commit and this fixes all the PHPUnit tests for Drupal 11, see below:
But probably this might cause failures in Previous Minor or Previous Major Drupal. If Yes, then can you please see from here, If you can update the tests accordingly, so that it works on all supported Drupal versions.
Thanks. - Status changed to Needs work
6 months ago 10:40am 29 May 2024 - last update
6 months ago 55 pass - last update
6 months ago 52 pass, 2 fail - last update
6 months ago 55 pass - last update
6 months ago 55 pass - last update
6 months ago 55 pass - last update
6 months ago 55 pass - Status changed to Needs review
6 months ago 2:53pm 2 June 2024 - last update
6 months ago 55 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.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
- last update
6 months ago 55 pass - last update
6 months ago 55 pass - last update
6 months ago 55 pass - last update
6 months ago 55 pass - last update
6 months ago run-tests.sh fatal error - last update
6 months ago 55 pass - 🇮🇳India rajeshreeputra Pune
The CKE4to5 upgrade test is failing in the upcoming minor and major versions due to a new requirement stipulating that the provider function must be declared as static starting with version 10.3 and beyond. However, in Drupal 10.2 and previous versions, the CKE5 SmartDefaultSettingsTest provider method is not static.
We would greatly appreciate the input of the maintainer and community.
- First commit to issue fork.
- Status changed to Fixed
6 months ago 4:40pm 8 June 2024 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India vishalkhode
@ufku: Looks like we've missed merging schema changes and it's causing our PHPUnit tests to fail. Ref: 🐛 missing schema exception in Drupal 11 Active : Can we please get that merged ?