- 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
- Merge request !8Issue #3433535: Automated Drupal 11 compatibility fixes for multiselect → (Merged) created by project update bot
- Status changed to Fixed
about 1 year ago 2:14am 26 March 2024 - 🇨🇦Canada mparker17 UTC-4
This looks good to me; merging.
We should probably add CI/CD config to this module so we can better test patches.
- Status changed to RTBC
about 1 year ago 2:21pm 26 March 2024 - 🇨🇦Canada mparker17 UTC-4
Hmm... keep getting merge errors. Moving back to RTBC, might have to rebase.
-
mparker17 →
committed 294b1c73 on 2.x authored by
Project Update Bot →
Issue #3433535: Automated Drupal 11 compatibility fixes for multiselect
-
mparker17 →
committed 294b1c73 on 2.x authored by
Project Update Bot →
- Status changed to Fixed
about 1 year ago 5:12pm 26 March 2024 Automatically closed - issue fixed for 2 weeks with no activity.