can't use guzzlehttp 6.x,please update dependecy

[argb]

I can't this sdk,because you still use old guzzlehttp 5.x,it's really sorry for that.

[colin-stannard]

This is a problem for me too. Any chance of an upgrade soon?

[argb]

@colin-stannard Finally ,I removed all packages depend on Guzzlehttp 6.

[RubenKruiswijk]

You could also use "mailgun/mailgun-php": "1.7.2" (which relies on the older guzzle/http) and guzzlehttp 6 together while waiting on the rewrite (see pull requests)

[argb]

@RubenKruiswijk Thank you for your advices.

[DonnieDrummer]

I'm too need support guzzlehttp ~6.0

[perajovic]

+1

[joshfoskett]

Would love to see support for Guzzle 6, this is holding me back.

[brynnb]

Also looking forward to this, having to remove mailgun from my project until guzzle is updated/replaced. Thanks for all the hard work!

[RubenKruiswijk]

@DonnieDrummer, @perajovic, @RastaLulz, @brynnb please see my comment above. Version 1.7.2 is working just fine and provides the same functionality.

[brynnb]

@RubenKruiswijk thanks for the note, unfortunately I am relying on another library that relies on 1.8+, I am not using mailgun-php directly, so the lack of guzzle 6 is still an issue for me.

[olsgreen]

+1 using @RubenKruiswijk work around atm.

[uaoleg]

+1

v1.7.2 has some weird constants implementation which causes such an error:

PHP Notice 'yii\base\ErrorException' with message 'Use of undefined constant RECIPIENT_COUNT_LIMIT - assumed 'RECIPIENT_COUNT_LIMIT''

in \vendor\mailgun\mailgun-php\src\Mailgun\Messages\MessageBuilder.php:88

[Nyholm]

PR #94 will allow you to decide what version of Guzzle to use. Please review it and test it so it will be easy for the maintainers to make a decision to merge or not.

[mollierobbert]

+1 it should work with guzzlehttp 6.

[DSpeichert]

+1

[renzell]

+1

[dbebawy]

+1

[Nyholm]

With Guzzle 6 (and 5) can be used in the version 2.0