- Issue created by @project update bot
- last update
7 months ago 20 pass 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-185226These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.1
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.1
- last update
7 months ago 20 pass 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-188138These 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
-
greggles β
committed 2a6012f5 on 8.x-1.x
Issue #3450694: Automated Drupal 11 compatibility fixes for...
-
greggles β
committed 2a6012f5 on 8.x-1.x
- πΊπΈUnited States greggles Denver, Colorado, USA
OK, I committed this to 8.x-1.x branch and we could create a release from that if there's no bugs reported in the next few weeks.
- First commit to issue fork.
- π―π΅Japan ptmkenny
@greggles Can we get this committed to the 2.x branch as well please? I added an MR on the
drupal11
branch (in retrospect, I should've named it something like 2.x-drupal11). -
greggles β
committed e4e62116 on 2.x authored by
ptmkenny β
Issue #3450694 by greggles: Automated Drupal 11 compatibility fixes for...
-
greggles β
committed e4e62116 on 2.x authored by
ptmkenny β
- πΊπΈUnited States greggles Denver, Colorado, USA
That's a nice small change as well. Generally other maintainers are working on the 2.x branch, but given how small it is I merged it.
I forgot to give you credit before clicking merge, but I'm doing that now. Cheers.
- π¦πΊAustralia VladimirAus Brisbane, Australia
VladimirAus β changed the visibility of the branch project-update-bot-only to hidden.
- π¦πΊAustralia VladimirAus Brisbane, Australia
VladimirAus β changed the visibility of the branch 3450694-automated-drupal-11 to hidden.
- Status changed to Fixed
5 months ago 6:27pm 5 August 2024 - π«π·France andypost
Thank you, tagged https://www.drupal.org/project/email_registration/releases/2.0.0-rc7 β
Automatically closed - issue fixed for 2 weeks with no activity.