Automated Drupal 11 compatibility fixes for pathauto

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

We need to rebase with 8.x-1.x since the failing tests have already been fixed here.

Was a bit of a fight to get next major working due to ctools and current deprecation issues, also had to fix a minor but annoying to investigate ajax deprecation issue. Merged.

Note: I had temporarily enabled next minor/major testing, but removed it again, there is now a weekly scheduled pipeline testing those. QI also had to remove previous major testing due to the forum dev dependency. Will need to add that back when previous major is updated to be D10.

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

Thanks for maintaining Pathauto @berdir. Since Drupal 11 release is very close now (in about two weeks) would it make sense to make a Drupal 11 ready release in advance?

Week of July 29, 2024 (UTC) | Drupal 11.0.0 released.

https://www.drupal.org/about/core/policies/core-release-cycles/schedule#... →

Hello @Berdir,

Given that Drupal 11 is nearing its release, will we see a stable version of this module beforehand? Thanks!

Please don't add repeated comments asking for commits or releases. You can't ping people on drupal.org. Either the maintainer won't see your comment so it won't do anything, or you'll just annoy them if they already follow and everyone else who happens to follow those issues.

It takes time to maintain the issue queue in a project like Pathauto, there are a lot of needs review and RTBC issues that I typically go through before a new release. If you actually want to help getting releases out, then help going through those issues, make sure that they use merge requests and not patches, that they still apply and fix what they should, that coding standards and so on are correct and there aren't too many unrelated changes, write tests and so on.

Hello @berdir,

I am completely agree with you that it takes time to release stable releases by covering all the corner cases with all the different issues logged. Please accept my sincere apologies if it hurts by my followup, but my intention is to learn the timeline of this module so that Acquia CMS Common → module can be planned accordingly. I will ensure you do not receive further followups on any other tickets and apologize again if I upset you in any way. Thanks for the stable release too and unblocking us.