- Issue created by @project update bot
- last update
9 months ago 86 pass 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 86 pass - last update
9 months ago 86 pass 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
- First commit to issue fork.
- πΊπΈUnited States michaellander
michaellander β changed the visibility of the branch 3431022-automated-drupal-11 to hidden.
- πΊπΈUnited States michaellander
michaellander β changed the visibility of the branch project-update-bot-only to hidden.
- πΊπΈUnited States michaellander
I've added the necessary
core_version_requirement
and tested in Drupal 11, and all looks good. - First commit to issue fork.
- π¦πΊAustralia acbramley
Pulled CI file from β¨ Add Gitlab CI file Active and added
OPT_IN_TEST_NEXT_MAJOR
- π¬π§United Kingdom steven jones
steven jones β made their first commit to this issueβs fork.
-
steven jones β
committed e19091b2 on 4.x authored by
michaellander β
Issue #3431022 by Project Update Bot, michaellander, steven jones,...
-
steven jones β
committed e19091b2 on 4.x authored by
michaellander β
Automatically closed - issue fixed for 2 weeks with no activity.