- Issue created by @project update bot
- Status changed to Needs review
5 months ago 11:52pm 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
- First commit to issue fork.
- 🇯🇵Japan ptmkenny
Created a new branch, added D11 to info.yml, and applied the rector patch.
However, the MR is giving the following error and I don't understand why:
Project `drupalspoons/webmasters` not found or access denied! Make sure any includes in the pipeline configuration are correctly defined.
- 🇪🇸Spain rodrigoaguilera Barcelona
I think the branch you created doesn't start from the latest 2.x from yesterday.
D11 compatibility is already declared
- 🇯🇵Japan ptmkenny
Sorry, somehow I missed that. Feel free to close my MR then; I tried to close it myself, but all I can see is the pipeline error screen.
- Status changed to Fixed
5 months ago 2:21pm 20 June 2024 - 🇪🇸Spain rodrigoaguilera Barcelona
I tried to merge it some days ago but I couldn't. It kept on creating merge trains
Automatically closed - issue fixed for 2 weeks with no activity.