Contrib.social

Automated Drupal 11 compatibility fixes for mailgun

Open on Drupal.org →
Created on 30 May 2024, about 1 year ago

Problem/Motivation

Hello project maintainers,

This is an automated issue to help make this module compatible with Drupal 11.

Changes will periodically be added to this issue that remove deprecated API uses. To stop further changes from being posted, change the status to anything other than Active, Needs review, Needs work or Reviewed and tested by the community. Alternatively, you can remove the "ProjectUpdateBotD11" tag from the issue to stop the bot from posting updates.

The changes will be posted by the Project Update Bot → official user account. This account will not receive any issue credit contributions for itself or any company.

Proposed resolution

You have a few options for how to use this issue:

  1. Accept automated changes until this issue is closed

    If this issue is left open (status of Active, Needs review, Needs work or Reviewed and tested by the community) and the "ProjectUpdateBotD11" tag is left on this issue, new changes will be posted periodically if new deprecation fixes are needed.

    As the Drupal Rector project improves and is able to fix more deprecated API uses, the changes posted here will cover more of the deprecated API uses in the module.

    Patches and/or merge requests posted by others are ignored by the bot, and general human interactions in the issue do not stop the bot from posting updates, so feel free to use this issue to refine bot changes. The bot will still post new changes then if there is a change in the new generated patch compared to the changes that the bot posted last. Those changes are then up to humans to integrate.

  2. Leave open but stop new automated changes.

    If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated changes, remove the "ProjectUpdateBotD11" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated changes again, add back the "ProjectUpdateBotD11" tag.

  3. Close it and don't use it

    If the maintainers of this project don't find this issue useful, they can close this issue (any status besides Active, Needs review, Needs work and Reviewed and tested by the community) and no more automated changes will be posted here.

    If the issue is reopened, then new automated changes will be posted.

    If you are using another issue(s) to work on Drupal 11 compatibility it would be very useful to other contributors to add those issues as "Related issues" when closing this issue.

Remaining tasks

Using the patches

  1. Apply the latest patch in the comments by Project Update Bot → or human contributors that made it better.
  2. Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.

Using the merge request

  1. Review the merge request and test it.
  2. Thoroughly test the changes. These changes are automatically generated so they haven't been tested manually or automatically.
  3. Provide feedback about how the testing went. If you can improve the merge request, create a new branch and merge request and work from there.

Warning: The 'project-update-bot-only' branch will always be overwritten. Do not work in that branch!

Providing feedback

If there are problems with one of the changes posted by the Project Update Bot → , such as it does not correctly replace a deprecation, you can file an issue in the Drupal Rector issue queue → . For other issues with the bot, for instance if the issue summary created by the bot is unclear, use the Project analysis issue queue → .

📌 Task
Status

Needs review

Version

2.0

Component

Code

Created by

project update bot

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @project update bot
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & sqlite-3.27
    last update about 1 year ago
    5 pass
  • Comment about 1 year ago →
    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 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

    Bot run #11-185727

    These packages were used to generate the fixes:

    1. drupal/upgrade_status: 4.3.1
    2. mglaman/phpstan-drupal: 1.2.11
    3. palantirnet/drupal-rector: 0.20.1
  • Merge request !26Automated Project Update Bot fixes → (Open) created by project update bot
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & sqlite-3.27
    last update about 1 year ago
    5 pass
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & sqlite-3.27
    last update about 1 year ago
    5 pass
  • Comment about 1 year ago →
    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 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

    Bot run #11-188815

    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
  • Open in Jenkins → Open on Drupal.org →
    Core: 10.2.1 + Environment: PHP 8.1 & sqlite-3.27
    last update about 1 year ago
    5 pass
  • Status changed to Needs work 4 months ago
  • Comment 4 months ago →
    🇧🇬Bulgaria pfrenssen Sofia

    Just updating the version strings is not sufficient. I did a check and the following issues also need to be addressed:

    1. Class Drupal\mailgun\Commands\MailgunSanitizeCommands implements deprecated interface Drush\Drupal\Commands\sql\SanitizePluginInterface: use \Drush\Commands\sql\sanitize\SanitizePluginInterface instead.
    2. MailgunMail.php, line 111: Call to deprecated method renderPlain(). Deprecated in drupal:10.3.0 and is removed from drupal:12.0.0. Use Drupal\Core\Render\RendererInterface::renderInIsolation() instead.
  • Comment 3 months ago →
    🇨🇴Colombia diegoluisr

    I've created a patch with recomendations from Update Status module.

  • Comment 3 months ago →
    🇺🇦Ukraine knyshuk.vova

    knyshuk.vova → made their first commit to this issue’s fork.

  • Merge request !27Issue #3451175: Drupal 11 compatibility fixes. → (Open) created by knyshuk.vova
  • Comment 3 months ago →
    🇺🇦Ukraine knyshuk.vova

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

  • Comment 3 months ago →
    🇺🇦Ukraine knyshuk.vova

    knyshuk.vova → changed the visibility of the branch 3451175-automated-drupal-11 to hidden.

  • Comment 3 months ago →
    🇺🇦Ukraine knyshuk.vova

    Merge request !27
    I was able to configure the module and send an email using version 2.0.0 of the module.

  • Comment 3 months ago →
    🇺🇸United States jphelan

    Patch is working for me on Drupal 11.1.5

  • Comment about 2 months ago →
    🇮🇳India keshavv India

    Could someone please proceed with releasing the tag for Drupal 11?

  • Status changed to RTBC about 1 month ago
  • Comment about 1 month ago →
    🇺🇸United States AaronBauman Philadelphia

    MR27 gtg please merge.

  • First commit to issue fork.
  • Comment 17 days ago →
    🇺🇸United States dcam

    I'll argue that a module isn't "good to go" if its automated tests aren't running, which was the case here because a .gitlab-ci.yml hadn't been added yet. I added one and am setting the status back to Needs Review. A maintainer needs to review the testing configuration and enable/disable options that they want to support.

    I also removed Drupal 9 from all of the info.yml Core compatibility strings. GitLab CI can't test against it, so you can't guarantee compatibility. A breaking change may be introduced and you wouldn't know until someone filed a bug report unless you're running the tests yourself. I've done this in the modules I maintain and encourage others to do the same. I typically release a new minor version when doing this. It isn't necessary to release a new major version.

    As for everyone else asking for this to be committed: I checked the most recently-active maintainer's user profile page. He mentions that he's been serving in the Ukrainian National Guard. So I wouldn't expect a fast response. My own plan is to copy the module and this compatibility fix to a private GitHub mirror until an update is made. I'm not interested in maintaining the module because I know nothing about it or the Mailgun service yet. This is my first day of using it.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024