- 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
- π¨π¦Canada dstorozhuk Chicago πΊπΈ, Toronto π¨π¦, Kyiv πΊπ¦
Merged. If that the only change we need to be compatible with D11 - then great π.
- π¬π§United Kingdom intrafusion Edinburgh, UK
Any chance of a tagged release?
- π§πͺBelgium weseze
I have tagged a new release, but unable to actually publish the release. I'm missing permissions for that...
- π¦πΊAustralia acbramley
Hi @weseze, are you able to contact any of the other maintainers to action this?
- π§πͺBelgium weseze
No, I don't have any direct contact info for any of the maintainers... (also don't know who actually has permission to publish releases)
- π¨π¦Canada dstorozhuk Chicago πΊπΈ, Toronto π¨π¦, Kyiv πΊπ¦
I will check and create a release shortly.
You can always reach me in slack https://drupal.slack.com/archives/D01F4DBR9C1 .
- π¨π¦Canada dstorozhuk Chicago πΊπΈ, Toronto π¨π¦, Kyiv πΊπ¦
Does anyone tested that update?
- π¨π¦Canada dstorozhuk Chicago πΊπΈ, Toronto π¨π¦, Kyiv πΊπ¦
Since all in that thread were pushing to merge the proposed update I expected that at least someone tested the update. However, as fast as I can see - the update still needs some work to be done. For some reasons ate least in Drupal 10.4.2 and D11 - forms UI cache is not invalidated after module installation.
- π¨π¦Canada dstorozhuk Chicago πΊπΈ, Toronto π¨π¦, Kyiv πΊπ¦
I added a PR here https://git.drupalcode.org/project/account_field_split/-/merge_requests/10 .
Please review and test on D10 and up.