- last update
over 1 year ago 223 pass This is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module → , even with this patch, this module is not yet compatible with Drupal 10.
Currently Drupal Rector, version 0.15.1, cannot fix all Drupal 10 compatibility problems.
Therefore this patch does not update the
info.yml
file for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot → to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #12554This patch was created using these packages:
- mglaman/phpstan-drupal: 1.1.35
- palantirnet/drupal-rector: 0.15.1
- Status changed to Active
over 1 year ago 5:14pm 4 July 2023 - 🇬🇧United Kingdom jonathan1055
As per comment in #20 the
eventDispatcher->dispatch
parameter is and must not be chnaged as per the automated patch in #22. Is there a way to state this in the code, to prevent the patch being repeatedly added? - 🇺🇸United States bvoynick
The ticket description says removing a tag will work to stop bot activity going forward:
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then).
Since this was the only thing the bot found, removing the tag and marking this fixed seems fine? But I'll leave that choice to you @jonathan1055
- 🇬🇧United Kingdom jonathan1055
I was leaving the issue open in case the bot reports anything new. But I do not know how or if the bot is being updated to report new things. I will leave open for now, but if you have any info on whether the bot is being updated or expanded then let me know. Thanks.
- Status changed to Fixed
3 months ago 11:56am 24 September 2024 Automatically closed - issue fixed for 2 weeks with no activity.