- Issue created by @project update bot
- last update
11 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-120024This 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
11 months ago PHPLint Failed - last update
11 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
11 months ago PHPLint Failed - 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 (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
8 months ago PHPLint Failed - First commit to issue fork.
- πΊπΈUnited States brayn7 Lexington, Ky
brayn7 β changed the visibility of the branch 3428529- to hidden.
- πΊπΈUnited States brayn7 Lexington, Ky
I created a branch off of the automatic updates called: https://git.drupalcode.org/issue/components-3428529/-/tree/3428529-upgra...
WIth the dev branch on 10.3, php 8.3, Upgrade status is happy and site runs.
- Status changed to RTBC
7 months ago 6:52pm 9 August 2024 - π¬π§United Kingdom darren.fisher
This looks good to me too! Can this be merged so we can start preparing for D11 support?
- First commit to issue fork.
- Status changed to Needs work
6 months ago 3:24pm 16 August 2024 - π¨π¦Canada RobLoach Earth
Sounds like there were some chnages to the pipeline? Mind having another look at the test results and pulling the latest into this new branch? Thanks!
- π¦πΊAustralia acbramley
acbramley β changed the visibility of the branch 3428529-automated-drupal-11 to hidden.
- Assigned to acbramley
- π¦πΊAustralia acbramley
Working on these tests today, there's a huge amount to fix in there.
- Issue was unassigned.
- Status changed to Needs review
6 months ago 2:30am 20 August 2024 - π¦πΊAustralia acbramley
acbramley β changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to Needs work
6 months ago 5:15am 22 August 2024 - Status changed to Needs review
6 months ago 12:08am 23 August 2024 - π¦πΊAustralia acbramley
You're right, I've dropped unsupported versions.
- Status changed to RTBC
6 months ago 6:05am 9 September 2024 - πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
@robloach This is needed for demoing something at DrupalCon Barcelona. Any chance it can get committed this week?
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
Actually bumping to critical since itβs for a starshot thing
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
@acbramley said he'll get this in asap π
-
acbramley β
committed e3f631a1 on 3.x authored by
brayn7 β
Issue #3428529 by acbramley, brayn7, jeremy1606, mstrelan, robloach:...
-
acbramley β
committed e3f631a1 on 3.x authored by
brayn7 β
- Status changed to Fixed
6 months ago 10:49pm 9 September 2024 Automatically closed - issue fixed for 2 weeks with no activity.