- Issue created by @project update bot
- last update
9 months ago 1 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 → 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
9 months ago 1 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 → 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-188138These 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
- First commit to issue fork.
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch 3450893-automated-drupal-11-fixes to hidden.
- 🇮🇳India deepakkm
deepakkm → changed the visibility of the branch 3450893-automated-drupal-11-fix to hidden.
- First commit to issue fork.
- 🇮🇳India chandu7929 Pune
chandu7929 → changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to RTBC
7 months ago 4:14pm 20 August 2024 - 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
$ git apply -v 11.patch Checking patch .gitlab-ci.yml... Checking patch composer.json... Checking patch bg_image_formatter.info.yml... Checking patch modules/responsive_bg_image_formatter/responsive_bg_image_formatter.info.yml... Applied patch .gitlab-ci.yml cleanly. Applied patch composer.json cleanly. Applied patch bg_image_formatter.info.yml cleanly. Applied patch modules/responsive_bg_image_formatter/responsive_bg_image_formatter.info.yml cleanly.
Upgrade status goes green. RTBC from here +1
- 🇨🇦Canada joseph.olstad
We've been using this merge request with Drupal 11.1.1 and now Drupal 11.1.2 since mid January. No issues reported after 500 hours of testing. Works in D11 as it did in D10.
Automatically closed - issue fixed for 2 weeks with no activity.