- Issue created by @project update bot
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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Status changed to Needs review
about 1 year ago 6:34am 25 March 2024 - First commit to issue fork.
-
larowlan →
committed e1f3f63b on 3.x authored by
Project Update Bot →
Issue #3435730: Automated Drupal 11 compatibility fixes for...
-
larowlan →
committed e1f3f63b on 3.x authored by
Project Update Bot →
- First commit to issue fork.
- First commit to issue fork.
- Merge request !23Issue#3435730: D11 support and updating gitlab template. → (Merged) created by ankitv18
- Status changed to Needs work
11 months ago 10:07am 21 May 2024 - 🇮🇳India vishalkhode
@ankitv18: Looks like there are couple of deprecations that needs to be fixed. I think the warnings are coming because return type of methods not defined. Ex:
public function testDelivery($pluginId, array $expectedRecipients, array $settings = [], array $expectedDependencies = []) { // It should be public function testDelivery($pluginId, array $expectedRecipients, array $settings = [], array $expectedDependencies = []): void {
Can we add this in all methods of test and see if warnings are fixed ?
- Status changed to Needs review
11 months ago 11:23am 21 May 2024 - 🇮🇳India ankitv18
Deprecation warnings are basically from twig, doctrine and other drupal core packages,
example:The "Twig\Environment::getTemplateClass()" method is considered internal. It may change without further notice.
We can ignore these deprecations and will work once D11 have a stable release, please review MR!23 - Status changed to RTBC
11 months ago 1:00pm 21 May 2024 - 🇮🇳India vishalkhode
Review PR, changes looks good to me and also ran the tests in local and all are passing. The deprecations reported in "PHPUnit Next Major" are all related to Drupal core.
- 🇮🇳India ankitv18
Hey @larowlan,
Please review MR!23 as it consists all the required changes for D11 compatiblity. - 🇮🇳India vishalkhode
vishalkhode → changed the visibility of the branch project-update-bot-only to hidden.
- 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
Thanks will look at this later in the week
-
larowlan →
committed 4c9ecb48 on 3.x authored by
ankitv18 →
Issue #3435730: Automated Drupal 11 compatibility fixes for...
-
larowlan →
committed 4c9ecb48 on 3.x authored by
ankitv18 →
- Status changed to Fixed
10 months ago 4:37am 5 June 2024 Automatically closed - issue fixed for 2 weeks with no activity.