- 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
murat_kekic โ made their first commit to this issueโs fork.
- First commit to issue fork.
- ๐ฌ๐งUnited Kingdom rachel_norfolk UK
rachel_norfolk โ changed the visibility of the branch project-update-bot-only to hidden.
- ๐ฌ๐งUnited Kingdom rachel_norfolk UK
Added comment to say we donโt need to drop support for ^8.8 at this stage - unless there is something Iโve missed?
- ๐ณ๐ฟNew Zealand Gold 20 minutes in the future
I have to agree with @rachel_norfolk. Dropping ^8.8 shouldn't be done in this ticket.
The MR at merge request !27 is the one to go with.
- First commit to issue fork.
- ๐บ๐ธUnited States joelsteidl
@rachel_norfolk @gold, I added
^8.8
back.I tested in D11 and feel good about it. Anyone else want to give it a test drive?
-
rachel_norfolk โ
committed 9b7a11a7 on 3.x authored by
sakthi_dev โ
Issue #3435552 by joelsteidl, murat_kekic, sakthi_dev, rachel_norfolk,...
-
rachel_norfolk โ
committed 9b7a11a7 on 3.x authored by
sakthi_dev โ
- ๐บ๐ธUnited States joelsteidl
Welcome! I'm curious if there is a timeline around getting a release out for D11 support?
- ๐ฌ๐งUnited Kingdom rachel_norfolk UK
No worries!
Honestly, I want to get a release out as much as you.
There are four or five issues that have been touched recently - either at Needs Work or Needs Review. Moving those through to RTBC will be key to getting that release out.