- Issue created by @Project Update Bot
- last update
8 months ago 1 fail 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-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
- last update
8 months ago 1 fail The last submitted patch, 2: protected_file.8.x-1.4.rector.patch, failed testing. View results →
- Status changed to Needs review
5 months ago 3:11am 18 June 2024 - Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
43:41 43:41 Queueing 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-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
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7
43:28 43:28 Queueing The last submitted patch, 5: protected_file.1.x-dev.rector.patch, failed testing. View results →
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.- Status changed to Active
about 1 month ago 1:52pm 10 October 2024 - cb8a24e2 committed on 2.0.x
Issue #3434022 by flocondetoile: Automated Drupal 11 compatibility fixes...
- cb8a24e2 committed on 2.0.x
- 0023339c committed on 2.0.x
Issue #3434022 by flocondetoile: Automated Drupal 11 compatibility fixes...
- 0023339c committed on 2.0.x
- 62ef0874 committed on 2.0.x
Issue #3434022 by flocondetoile: Automated Drupal 11 compatibility fixes...
- 62ef0874 committed on 2.0.x
- 35951383 committed on 2.0.x
Issue #3434022 by flocondetoile: Automated Drupal 11 compatibility fixes...
- 35951383 committed on 2.0.x
- 3e905c1c committed on 2.0.x
Issue #3434022 by flocondetoile: Automated Drupal 11 compatibility fixes...
- 3e905c1c committed on 2.0.x
- f33db833 committed on 2.0.x
Issue #3434022 by flocondetoile: Automated Drupal 11 compatibility fixes...
- f33db833 committed on 2.0.x
Automatically closed - issue fixed for 2 weeks with no activity.