Automated Drupal 11 compatibility fixes for composer_deploy

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

This patch was created using these packages:

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

Balu Ertl → made their first commit to this issue’s fork.

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

MR !6 is tested on a D11-beta1 site, *-dev version numbers appears properly under the name of modules installed not from Drupal․org.

1. Minimum required version of core bumped to ^9.5.11
2. Minimum required version of webflo/drupal-finder bumped to ^1.3
3. PHP 8.1 required directly due to the previous point

Not sure whether that's related, but even with the module enabled on D11.0.1, I do see the contrib updates, flagged as invalid for MR branches, but no core releases. It looks like it could be related to 🐛 Error when there is no Drupal project name.info.yml file Needs review , because there is no `drupal.info.yml` in core, but that's just an idea.

Thanks @balu_ertl for having worked on this. Do you need help with something so we can get that release ?

Also, it does not show the synthetic dev version numbers for me, giving the branch name instead, as in this screenshot.

@fgm - synthetic dev version numbers will be shown when we pull the dev released branch of that module , in our case backup_migrate.
When you see i pulled up dev branch of that module and i can see the right versioning in it

Thanks to all. I have published a new release.

Please remove webmozart/path-util from the composer.json file if it is no longer in use. It is causing a message about "abandoned package" during "composer audit". See https://www.drupal.org/project/composer_deploy/issues/3473097 📌 webmozart/path-util is abandoned Active

deepakkm → changed the visibility of the branch 3429433-removed-path-util-package to hidden.

deepakkm → closed merge request !11

Please remove webmozart/path-util from the composer.json file if it is no longer in use. It is causing a message about "abandoned package" during "composer audit" - this is fixed in the latest release of the module, please see this - https://www.drupal.org/project/composer_deploy/releases/8.x-1.8 →

Thanks @deepakkm. Just to confirm, it appears to be fixed in 8.x-1.x (dev) but not 8.x-1.8.

Confirming that this is still requiring webmozart/path-util in 8.x-1.8.

Fixed in https://www.drupal.org/project/composer_deploy/releases/8.x-1.9 →

Thank you. Release 8.x-1.9/10 fixed the audit issue.

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