- Issue created by @project update bot
- last update
9 months ago Patch Failed to Apply 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
- Open on Drupal.org βCore: 10.2.x + Environment: PHP 8.1 & pgsql-14.1last update
9 months ago Not currently mergeable. - Status changed to RTBC
9 months ago 11:53am 25 March 2024 - πΊπΈUnited States mradcliffe USA
The MR doesn't apply because the module is already fixed.
- Status changed to Needs work
9 months ago 1:13pm 25 March 2024 - Merge request !4Issue #3435282 by mradcliffe: Fixes Drupal 11 compatibility β (Merged) created by mradcliffe
- last update
9 months ago 23 pass - last update
9 months ago 23 pass - last update
9 months ago 23 pass -
mradcliffe β
committed 308a5a10 on 1.0.x
Issue #3435282 by mradcliffe: Automated Drupal 11 compatibility fixes...
-
mradcliffe β
committed 308a5a10 on 1.0.x
- Status changed to RTBC
9 months ago 1:42pm 25 March 2024 - Status changed to Needs review
6 months ago 4:50am 18 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
- Merge request !5Issue #3435282: Fixes compatability for Drupal 11 β (Merged) created by mradcliffe
-
mradcliffe β
committed 2f77f1d8 on 1.0.x
Issue #3435282 by mradcliffe: Automated Drupal 11 compatibility fixes...
-
mradcliffe β
committed 2f77f1d8 on 1.0.x
- Status changed to Fixed
6 months ago 12:55pm 19 June 2024 - πΊπΈUnited States mradcliffe USA
Well, that's unfortunate. A backwards-compatible change in the test framework that causes failures in 11, but not 10.
It looks like it will not be possible to make a backwards-compatible release between releases due to Drupal core.
I'm going to ahead and merge in MR 5, but then this issue will be set to fixed and a new branch created.
Automatically closed - issue fixed for 2 weeks with no activity.