- Issue created by @project update bot
- last update
9 months ago 4 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 4 pass - last update
9 months ago 4 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
- last update
9 months ago 4 pass - last update
7 months ago Composer require failure 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 β these changes make this module compatible with Drupal 11! π
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.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-185727These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
7 months ago Composer require failure - First commit to issue fork.
- last update
7 months ago Composer require failure - last update
7 months ago 4 pass - last update
7 months ago 4 pass - last update
7 months ago 4 pass - last update
7 months ago 4 pass - last update
7 months ago PHPLint Failed - last update
7 months ago PHPLint Failed - last update
7 months ago PHPLint Failed - last update
7 months ago PHPLint Failed -
Berdir β
committed f13e4367 on 8.x-4.x authored by
Project Update Bot β
Issue #3431789 by Project Update Bot: Automated Drupal 11 compatibility...
-
Berdir β
committed f13e4367 on 8.x-4.x authored by
Project Update Bot β
- Status changed to Fixed
7 months ago 6:44pm 1 June 2024 - ππΊHungary Balu Ertl Budapest πͺπΊ
Balu Ertl β made their first commit to this issueβs fork.
- Merge request !13Update the URL of a.d.o links with the latest core version number referenced β (Open) created by Balu Ertl
- ππΊHungary Balu Ertl Budapest πͺπΊ
Reopening issue to update the URL of a.d.o links with the latest core version number referenced.
- ππΊHungary Balu Ertl Budapest πͺπΊ
Balu Ertl β changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to Needs review
6 months ago 3:17pm 10 June 2024 - ππΊHungary Balu Ertl Budapest πͺπΊ
Balu Ertl β changed the visibility of the branch 8.x-4.x to hidden.
- Status changed to Fixed
6 months ago 4:20pm 10 June 2024 - π¨πSwitzerland berdir Switzerland
I think it make more sense as a separate issue, that's not actually necessary for D11 compatibility. Also, I think there's a way to remove the version from those links and it will pick the default.
- ππΊHungary Balu Ertl Budapest πͺπΊ
Pulling one hour of contributor work down the drain compared to rather improving the end-user experience by clicking a single Merge button.
- π¨πSwitzerland berdir Switzerland
All I'm asking is creating a separate issue with a new MR, nothing has been sent down any drain: π Update links in documentation Needs work , still needs work though.
Automatically closed - issue fixed for 2 weeks with no activity.