- Issue created by @project update bot
- last update
7 months ago 536 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
7 months ago 536 pass - First commit to issue fork.
- last update
7 months ago 536 pass - last update
7 months ago 536 pass - 🇨ðŸ‡Switzerland berdir Switzerland
Same as https://git.drupalcode.org/project/paragraphs/-/merge_requests/115/diffs..., you could try to get the ball rolling on D11 testing by using lenient for all test dependencies that aren't compatible yet.
- last update
6 months ago 536 pass - 🇨ðŸ‡Switzerland berdir Switzerland
Added lenient, also pushed to separate branch to not work on top of the bot branch.
- last update
6 months ago 536 pass - last update
6 months ago 536 pass - last update
6 months ago 536 pass - last update
6 months ago 536 pass - last update
6 months ago 536 pass - Status changed to Needs work
6 months ago 11:13pm 11 June 2024 - 🇨ðŸ‡Switzerland berdir Switzerland
lenient can't solve the conflict that devel currently has: https://gitlab.com/drupalspoons/devel/-/issues/527, temporarily removed from require-dev.
also made all submodules compatible and fixed an invalid namespace.
We have actual test fails now to work with.
- last update
6 months ago 537 pass - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
This issue should be only for automated fixes. Other fixes should be in a separate issue.
- Status changed to Needs review
6 months ago 5:11am 18 June 2024 - last update
6 months ago 536 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.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
- last update
6 months ago 536 pass - last update
6 months ago 537 pass - 🇨ðŸ‡Switzerland berdir Switzerland
The bot patches on their own aren't good enough to be committed IMHO, they are incomplete and can't be tested, automatically or manually. The additional manual changes are in a separate MR, which allows to easily cherry-pick commits from the bot branch in the same remote, which I just did with the latest updates. That's what I do for my projects and it works well IMHO.
That said, I just did a drive by to push this forward a bit, feel free to create a separate issue and commit the changes to new MR there. But then you probably want to close this or otherwise make it clear to other contributors to not work here, it's unlikely that the bot will do much more at this point.
- 🇮🇳India onkararun
Arun.k → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India onkararun
Arun.k → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India onkararun
Arun.k → changed the visibility of the branch project-update-bot-only to active.
- 🇮🇳India onkararun
Arun.k → changed the visibility of the branch project-update-bot-only to hidden.
- 🇮🇳India onkararun
Arun.k → changed the visibility of the branch project-update-bot-only to active.
- Status changed to Closed: duplicate
5 months ago 5:16pm 28 July 2024 - 🇨🇦Canada Liam Morland Ontario, CA 🇨🇦
Drupal 11 compatibility will be done on branch 6.3.x in 📌 Automated Drupal 11 compatibility fixes for webform Needs review . That ticket is only for automated fixes. Please make a fresh ticket for any other fixes.