Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Hello project maintainers,
This is an automated issue to help make this module compatible with Drupal 10.
To read more about this effort by the Drupal Association, please read: The project update bot is being refreshed to support Drupal 10 readiness of contributed projects
Patches will periodically be added to this issue that remove Drupal 10 deprecated API uses. To stop further patches 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 "ProjectUpdateBotD10" tag from the issue to stop the bot from posting updates.
The patches 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:
- Accept automated patches 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 "ProjectUpdateBotD10" tag is left on this issue, new patches 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 patches 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 patches. The bot will still post new patches then if there is a change in the new generated patch compared to the patch that the bot posted last. Those changes are then up to humans to integrate.
- Leave open but stop new automated patches.
If you want to use this issue as a starting point to remove deprecated API uses but then don't want new automated patches, remove the "ProjectUpdateBotD10" tag from the issue and use it like any other issue (the status does not matter then). If you want to receive automated patches again, add back the "ProjectUpdateBotD10" tag.
- 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 patches will be posted here.
If the issue is reopened, then new automated patches will be posted.
If you are using another issue(s) to work on Drupal 10 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
- Apply the latest patch in the comments by Project Update Bot or human contributors that made it better.
- Thoroughly test the patch. These patches are automatically generated so they haven't been tested manually or automatically.
- Provide feedback about how the testing went. If you can improve the patch, post an updated patch here.
Providing feedback
If there are problems with one of the patches 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.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | sending-email-test.png | 44.82 KB | bakop |
| #6 | Screenshot from 2023-05-24 15-41-55.png | 18.31 KB | dineshkumarbollu |
| #2 | mailjet_api.1.x-dev.rector.patch | 391 bytes | project update bot |
Issue fork mailjet_api-3288422
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
project update bot commentedThis is an automated patch generated by Drupal Rector. Please see the issue summary for more details.
It is important that any automated tests available are run with this patch and that you manually test this patch.
Drupal 10 Compatibility
According to the Upgrade Status module this patch makes this module compatible with Drupal 10! 🎉
This patch updates the
info.ymlfile for Drupal 10 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot to post additional Drupal 10 compatibility fixes as they become available in Drupal Rector.
Debug info
This patch was created using these packages:
Comment #3
project update bot commentedUpdating bot issue summary.See #3313904: Update project bot templates for RTBC status support and human interaction tips
Comment #4
kopeboyThe bot suggests we only add
|| ^10to the mailjet_api.info.yml file.Unfortunately fully testing this requires having a live site and account at mailjet, so I'm not changing the status to reviewed atm.
Maybe the maintainer could check if we can safely use this with D10 and provide a new release? 🙏🏻
Comment #6
dineshkumarbollu commentedHi
I review the patch applied cleanly, after that I test the d10 comaptible issues no issues found and module is compatible with D10.
I am attaching screenshot of upgrade status report for D10.
thanks
Comment #8
stevieb commentedI also confirm that the patch is working
Comment #9
flocondetoile@stevieb Are you using this module on D10. Can you confirm the module (with the patch) works on D10, and not only the patch (a working patch doesn't mean a working moduel) ?
Anybody else using mail_jet_api on D10 ? (not yet migrated on D10)
Comment #10
tty11Hello,
For information I wanted to install the module for D10 but I have an error with compose with a dependency of mailjet_api:
Core D10 requires guzzlehttp/guzzle ^7.5
mailjet/mailjet-apiv3-php since version 1.5.0 is ~7.0 compatible and the latest version is 1.5.9
Then I don't know if the module is compatible with mailjet/mailjet-apiv3-php >= 1.5.0
I'll try to do some tests, I'll keep you posted.
Comment #11
manikandank03 commentedHello,
I am also facing the same issue #10 in Drupal 10.1.1, unable to install the latest version of the module.
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires drupal/mailjet_api == 1.0.0.0 -> satisfiable by drupal/mailjet_api[1.0.0].
- drupal/mailjet_api 1.0.0 requires mailjet/mailjet-apiv3-php ~1.3.0 -> found mailjet/mailjet-apiv3-php[v1.3.0] but these were not loaded, likely because it conflicts with another require.
Please update the composer.json file with the latest mailjet-api version(https://github.com/mailjet/mailjet-apiv3-php) and release new version of the module.
"mailjet/mailjet-apiv3-php" : "^1.5"
Thanks.
Comment #13
bakopComment #14
bakopComment #15
bakopHi, there is indeed an issue with the version of the sdk to install the module on Drupal 10.
I did an email sending test (see attachment).
Comment #16
darvanenIf you come across this and are having trouble getting the module working, you can trick composer into resolving the library with
"mailjet/mailjet-apiv3-php": "1.6.0 as 1.3.0",Then the patch will take care of the rest.
So far it seems to me that the patch is all good but I'll hold off RTBCing it until it's gone through proper testing
Comment #17
flocondetoileCommitting MR5 to dev branch. I will be able to test on a real project soon. And so publish a new release if tests are OK.
Comment #19
flocondetoileLeaving open this issue until a new release is published.
Comment #20
flocondetoileLooks good.
Comment #21
darvanenHats off to you sir, many thanks for the release.