- 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 → 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
- First commit to issue fork.
- 🇮🇳India arunkumark Coimbatore
Reviewed the automated generated patch and found the issue on the Drupal 11.x. Updated the MR to work with Drupal core 11.x version.
- 🇦🇺Australia VladimirAus Brisbane, Australia
VladimirAus → changed the visibility of the branch 3434434-automated-drupal-11 to hidden.
- 🇦🇺Australia VladimirAus Brisbane, Australia
PHP Stan is good to go for Drupal 11.
PHPCS tasks were moved to 🐛 Create PHPCS fixes based on Gitlab CI Active . - Status changed to RTBC
8 months ago 3:40pm 14 May 2024 -
VladimirAus →
committed 9061546b on 8.x-1.x authored by
Project Update Bot →
Issue #3434434: Automated Drupal 11 compatibility fixes for securitytxt
-
VladimirAus →
committed 9061546b on 8.x-1.x authored by
Project Update Bot →
- Status changed to Fixed
8 months ago 4:06am 16 May 2024 Automatically closed - issue fixed for 2 weeks with no activity.