- 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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- Status changed to RTBC
7 months ago 3:07pm 13 March 2025 - πΊπΈUnited States davidburns Philadelphia
Confirmed it only needed ^11 version support in info.yml file.
- πΊπΈUnited States jcandan
If π Fix tests failing due to unknown option verbose Active gets adopted, you'll need to re-opt-in for Drupal 11 testing.
- πΊπΈUnited States jcandan
Do you still want to support Drupal 9? This might be worth making the breaking change for π± Require on Publish 8.x-1.11 or 2.0.0 stable release plan Active .
- πΊπΈUnited States alimc29
@jcandan - it looks like the latest changes broke the merge request, so a composer install on a fresh environment no longer works to patch
- πΊπΈUnited States jcandan
Yeah, sorry, this is in progress. Assigned to me. I am working out some testing kinks in π Ensure ConfigPageTest actually verifies require_on_publish setting Active first. I plan to get this out today.
- πΊπΈUnited States jcandan
Also...
so a composer install on a fresh environment no longer works to patch
@alimc29, I wouldn't rely on MR URLs for patches. It is best to use patch files uploaded to the issue or to commit them to your project.
However, don't fret--a release candidate supporting Drupal 11 is forthcoming. :)
Automatically closed - issue fixed for 2 weeks with no activity.