Automated Drupal 11 compatibility fixes for reroute_email

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 the info.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

These packages were used to generate the fixes:

1. drupal/upgrade_status: 4.1.0
2. mglaman/phpstan-drupal: 1.2.9
3. palantirnet/drupal-rector: 0.20.1

deepakkm → changed the visibility of the branch project-update-bot-only to hidden.

Fixed the pipelines

Reviewed changes, looks good to me. Hence, RTBC.

The changes look good, have been verified, and are working as expected. I will proceed with the merge, and we look forward to a release soon with a stable D11-compatible version.

@Rajeshreeputra @bohart Can we please get a stable/RC release for the same ? Thanks.

If a module does not have any dependencies, or the dependencies are solely other Drupal modules, then a composer.json is not required.
© drupal-org documentation

1) There is no need to commit composer.json to the module, as it will be generated by drupal-org packegist.
Are there any reasons for adding and maintaining the composer.json file?

2) The 2.2.x branch should not break the work with D9/D10, and its Drupal core version_requirement is not supposed to be lower than in 2.3.x (to follow semantic versioning).
All the changes must be committed either to 2.3.x only (if they break D9/D10) or to both 2.2.x/2.3.x (if they are valid for all D9/D10/D11).

@Rajeshreeputra, please do not create any new releases while we're proceeding with the topics above.

@bohart,

1) There is no need to commit composer.json to the module, as it will be generated by drupal-org packegist.
Are there any reasons for adding and maintaining the composer.json file?

Having a composer.json can simplify the local development process, CI/pipeline when using vcs paths.

2) The 2.2.x branch should not break the work with D9/D10, and its Drupal core version_requirement is not supposed to be lower than in 2.3.x (to follow semantic versioning).
All the changes must be committed either to 2.3.x only (if they break D9/D10) or to both 2.2.x/2.3.x (if they are valid for all D9/D10/D11).

Agree with you, 📌 Automated Drupal 11 compatibility fixes for reroute_email RTBC will be completed to support same core_version_requirement.

@bohart: I also believe that including a composer.json file in your Drupal module can still offer several benefits, even though it might be generated or handled by tools like drupal-org packagist.

@bohart, Can we get a stable release of the reroute email module 2.2.x now that all requirements for Drupal 11 readiness have been addressed?

All the changes needed for D11 have been committed at #3455294-21: Automated Drupal 11 compatibility fixes for reroute_email → .
Please see all the details on that issue.

Thanks.

bohart → closed merge request !81

Automatically closed - issue fixed for 2 weeks with no activity.