- 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-188815These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- π©πͺGermany Anybody Porta Westfalica
Now that D11 is out, any maintainer plans here?
- π©πͺGermany Grevil
I replaced the doctrine annotation with the new Drupal standard and adjusted the compatibility accordingly. Ready for review!
- π©πͺGermany Grevil
grevil β changed the visibility of the branch 3452010-automated-drupal-11 to hidden.
- π©πͺGermany Anybody Porta Westfalica
Thank you!
I think in a follow-up a basic test and gitlab ci should be added? (But has nothing to do with D11 here).
- Status changed to RTBC
2 months ago 2:36pm 4 February 2025 - π©πͺGermany rgpublic DΓΌsseldorf π©πͺ πͺπΊ
What needs to be done for at least a tentative -dev release? It would be quite helpful because currently this module alone keeps us from updating dozens of sites... :-(
- π©πͺGermany Grevil
What needs to be done for at least a tentative -dev release?
The maintainers need to review and merge the given fix. You could try contacting them.
- First commit to issue fork.
- π΅πͺPeru heilop
After resolving the conflicts in the MR, I tested it with Drupal 11, and it worked as expected. I will proceed with merging it.
-
heilop β
committed cc61cc29 on 1.0.x authored by
project update bot β
Issue #3452010 by project update bot, grevil, heilop, anybody: Automated...
-
heilop β
committed cc61cc29 on 1.0.x authored by
project update bot β
- π©πͺGermany Anybody Porta Westfalica
@heilop could you maybe tag a release, please?
- π΅πͺPeru heilop
This has been released in the las version.
Thank you all for your help!
- π©πͺGermany Anybody Porta Westfalica
@heilop thank you! I guess this should be set "Fixed" then and all helpers should be credited (checkboxes bottom)
- π©πͺGermany Anybody Porta Westfalica
PS: Please also see π Project is not covered by the security advisory policy Active
- π΅πͺPeru heilop
I'll try to get the security advisory for π Project is not covered by the security advisory policy Active in the next releases.
Thank you @anybody.
Automatically closed - issue fixed for 2 weeks with no activity.