- Issue created by @project update bot
- last update
12 months ago 9 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
12 months ago 9 pass - Status changed to RTBC
10 months ago 4:47pm 2 June 2024 - 🇺🇸United States John Franklin
While it may be a bit of a head scratcher to set the
core_version_requirement:
to'>=8.9 <11 || ^11'
, it's not wrong. The MR in 📌 Allow installation and testing with Drupal 11 Fixed is better, but this works. Marking this as RTBC. - First commit to issue fork.
- last update
9 months ago 9 pass - Status changed to Active
9 months ago 1:08am 3 June 2024 - 🇺🇸United States rlhawk Seattle, Washington, United States
Support for Drupal 11 was added in 📌 Allow installation and testing with Drupal 11 Fixed . I'll leave this open for any additional automatic updates.
- Status changed to Needs review
9 months ago 1:21am 9 June 2024 - last update
9 months ago 9 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.2, cannot fix all Drupal 11 compatibility problems.
Therefore, these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
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-194493These 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
- last update
9 months ago 9 pass - First commit to issue fork.
-
rlhawk →
committed 039c1062 on 8.x-1.x authored by
Project Update Bot →
Issue #3431507: Automated Drupal 11 compatibility fixes for key
-
rlhawk →
committed 039c1062 on 8.x-1.x authored by
Project Update Bot →
- 🇺🇸United States John Franklin
That doesn't look right.
user_password()
is a fallback for when thepassword_generator
service doesn't exist.It may be better to drop support for 9.x entirely and simplify that function a one-line wapper for the
password_generator
service. - 🇺🇸United States rlhawk Seattle, Washington, United States
Oof, you're right. That was my mistake. I'm not quite ready to drop support for versions of Drupal prior to 9.1, but I imagine we will do it fairly soon.
- Status changed to Active
8 months ago 11:47pm 3 July 2024