- Issue created by @project update bot
- last update
9 months ago 5 pass 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
- last update
9 months ago 5 pass - First commit to issue fork.
-
johnzzon β
committed 98678f77 on 8.x-1.x authored by
acbramley β
Resolve #3431589 "Automated drupal 11"
-
johnzzon β
committed 98678f77 on 8.x-1.x authored by
acbramley β
- π¦πΊAustralia mstrelan
Thanks for this! Can I suggest it be backported to the 8.x-1.x branch too?
- πΈπͺSweden johnzzon Gothenburg πΈπͺ
2.0.0 is the same as 8.x-1.x, just this fix applied. Going to semver required a major version increase according to Drupal.org. So an upgrade to 2.0.0 will work just as well for sites with 1.x installed.
- π¦πΊAustralia mstrelan
That may be true, but it does require a manual bump in composer.json from ^1.0 to ^2.0, and if there are no major changes I don't see any reason not to do it, as it will reduce friction ever so slightly for making the upgrade. This has been the approach many other contrib modules are taking to make the upgrade as painless as possible.
- πΈπͺSweden johnzzon Gothenburg πΈπͺ
Okay, sure, I can tag a 1.x release today as well.
Automatically closed - issue fixed for 2 weeks with no activity.