- 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
- Status changed to Needs work
10 months ago 9:59am 20 June 2024 -
psf_ →
committed 34a53210 on 1.1.x authored by
Project Update Bot →
Issue #3433693: Automated Drupal 11 compatibility fixes for...
-
psf_ →
committed 34a53210 on 1.1.x authored by
Project Update Bot →
- Status changed to Active
10 months ago 10:09am 20 June 2024 - First commit to issue fork.
- 🇺🇸United States koppie
I'm picking this up.
I tried installing openai_client on a D11 site, and got a composer error. I'm guessing we need to add something to composer.json, for compatibility - so I'm opening a new MR for that. Stay tuned...
- 🇺🇸United States koppie
Bad news: I can load the patch from the merge request, but composer doesn't work that way; it needs to see compatibility in the module's composer.json before it will download the file. Even with the drupal-lenient composer add-on, it doesn't work, because there's a requirement for the openai-php client library.
Good news: The solution is easy: merge the MR into the dev version of the module. This is RISKY because we are releasing a new version of the module before testing. However, it is the dev version of the module, so anyone using it should be aware that it is not meant for production sites.
Pardon our dust. Merge incoming!