- 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 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, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-121090This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- Merge request !7Issue #3429725 by Project Update Bot, naveenvalecha: Automated Drupal 11 compatibility fixes for custom_meta. → (Merged) created by Project Update Bot
- Status changed to Postponed
5 months ago 8:19am 16 June 2024 - 🇮🇳India naveenvalecha New Delhi
Postponed on 📌 Automated Drupal 11 compatibility fixes for metatag Needs review
- Status changed to Needs review
about 2 months ago 6:11am 1 October 2024 - 🇮🇳India naveenvalecha New Delhi
Enabled after https://www.drupal.org/project/metatag/releases/2.0.2 →
- 🇮🇳India naveenvalecha New Delhi
PR has been merged to 2.1.x
It will be rolled out in next release. -
naveenvalecha →
committed 2cc70576 on 2.1.x authored by
Project Update Bot →
Issue #3429725 by Project Update Bot, naveenvalecha: Automated Drupal 11...
-
naveenvalecha →
committed 2cc70576 on 2.1.x authored by
Project Update Bot →
Automatically closed - issue fixed for 2 weeks with no activity.