Automated Drupal 11 compatibility fixes for coffee

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 → , even with these changes, this module is not yet compatible with Drupal 11.

Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.

Therefore these changes did not 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

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

Please review the PR. I have also fixed some coding in the same PR. Rest all looks to me in the PR.

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.3.2
2. mglaman/phpstan-drupal: 1.2.11
3. palantirnet/drupal-rector: 0.20.2

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.3.2
2. mglaman/phpstan-drupal: 1.2.11
3. palantirnet/drupal-rector: 0.20.2

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

Not sure about dropping support for 9.x

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.3.4
2. mglaman/phpstan-drupal: 1.2.11
3. palantirnet/drupal-rector: 0.20.3

$ git apply -v coffee.1.x-dev.rector.patch
Checking patch coffee.info.yml...
Checking patch tests/src/Functional/CoffeeTest.php...
Checking patch tests/src/Kernel/CoffeeCommandsTest.php...
Applied patch coffee.info.yml cleanly.
Applied patch tests/src/Functional/CoffeeTest.php cleanly.
Applied patch tests/src/Kernel/CoffeeCommandsTest.php cleanly.

Upgrade status says Coffee supported now. No flaws yet detected. Works as usual. +1 RTBC

+1 for RTBC thanks !

Apply this MR for D11 now with:

...
    "repositories": {
        "https://packages.drupal.org/8": {
            "canonical": false,
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        },
        "https://drupal.org/node/3428399": {
            "canonical": false,
            "type": "vcs",
            "url": "https://git.drupalcode.org/issue/coffee-3428399.git"
        },
    },
...
    "require": {
        "drupal/coffee": "dev-3428399-automated-drupal-11",
    }
...

Love this module. +1 for commit to DEV

GitLab is failing, though...? I should be able to take care of those.

The "upgrade status" CI job is still failing but I'm not really sure what, if anything, to do there. It feels like a job that should be allowed to fail, but that's not a call I feel qualified to make. :)

Awesome work +1 @phenaproxima - seems most issues are fixed now. Local test works and even a temporary previous issue (not reported yet here) of this branch not showing any content in the popup list is also wiped out. RTBC from here.

Just noting that we have had to remove Coffee from Drupal CMS until it is D11 compatible. 📌 Switch our base to Drupal 11 Active

@klausi @michaelmol Anything left to do blocking progress? I know too well how life and time is limited more than often, so let me know if you need co-maintainer support to get a D11 ready release. I am there to join, if required. Feel free to add me anytime.

We can simply remove the usage of upgrade_status as gitlab template default branch is D11 so there won't be a next major release in anytime soon.

cc: @dqd @phenaproxima

Pipelines are passing ~~ we can plan a merge for this one. :)

MR!15 Makes this module compatible with Drupal 11. Functionality is working as expected.

RTBC +1

Thanks everyone! I have just created a new 2.x branch for future development and released the D11 compatible version 2.0.0.

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

Don't forget to credit the participants. 🤔

Sorry @vladimiraus - for some reason I thought the credit in the commit message triggers the credit system. Thanks for reporting it!