- 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-137198These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.10
- palantirnet/drupal-rector: 0.20.1
- Status changed to Needs review
about 1 year ago 9:28pm 4 April 2024 - First commit to issue fork.
- 🇮🇳India ankitv18
ankitv18 → changed the visibility of the branch project-update-bot-only to hidden.
- Status changed to RTBC
9 months ago 6:59am 19 July 2024 -
vipin.mittal18 →
committed ae49e8ce on 2.0.x authored by
ankitv18 →
Issue #3438711 "D11 readiness"
-
vipin.mittal18 →
committed ae49e8ce on 2.0.x authored by
ankitv18 →
- Status changed to Fixed
9 months ago 7:04am 19 July 2024 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇮🇳India vipin.mittal18 Greater Noida
Sure @zoeblair, I will be releasing soon as validating some other changes too. In the meantime, you can run at https://www.drupal.org/project/user_redirect/releases/2.0.x-dev →
Sounds great, thanks! I've already got that running on a live site with d11 and it seems to be working great.
- 🇮🇳India vipin.mittal18 Greater Noida
That's good to hear and will help me release it as soon as possible.