- Issue created by @project update bot
- last update
10 months ago 3 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-194493These 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
- Merge request !3Automated Project Update Bot fixes #3453452 → (Closed) created by project update bot
- last update
10 months ago 3 pass - last update
10 months ago 3 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
10 months ago 3 pass - First commit to issue fork.
- Status changed to Needs work
29 days ago 1:27pm 7 March 2025 - 🇫🇷France prudloff Lille
This says phpstan should not care about the format_size() call: https://www.drupal.org/node/3379306 →
But it does not seem to work. - 🇫🇷France prudloff Lille
prudloff → changed the visibility of the branch project-update-bot-only to hidden.
- 🇫🇷France prudloff Lille
I did some more tests and it seems @phpstan-ignore-next-line is not required when using backwardsCompatibleCall() with a deprecated method, but it is still required when using backwardsCompatibleCall() with a method that has been removed from the current version of Drupal.
- 🇫🇷France andypost
Gonna start 2.x with it, the rest should be fixed in follow-ups
-
andypost →
committed 58c9169b on 2.x authored by
prudloff →
Issue #3453452 by prudloff, project update bot, andypost: Automated...
-
andypost →
committed 58c9169b on 2.x authored by
prudloff →
- 🇫🇷France andypost
Created release https://www.drupal.org/project/xhprof/releases/2.0.0-beta1 →
Automatically closed - issue fixed for 2 weeks with no activity.