-
Notifications
You must be signed in to change notification settings - Fork 656
Conversation
Thank you very much. Could you send this PR to the 1.x branch as well? |
When can we expect a minor release that will include this commit? |
I still get #945 issue on clear Laravel 9 project. |
That's because a new realease hasn't been tagget yed. Temporary solution: set your composer dependancy to dev-master |
@bmbBAMBUS As a temporary solution until a new release is tagged, you can fork the repository and set a VCS at the top of your composer.json:
|
Oh sorry, didn't notice that release hasn't been tagged. @diegotibi , @tntsoft Thank you for advices! |
I just tagged a new 1.x release and will tag a new 2.x beta as well |
Do you have any plans to update the package to Laravel 9? I tested it now and I still have the same problem. |
This is definitely working. Make sure your composer file import looks like this:
|
this is the error Problem 1 |
Probably my fault, I've forgot to bump guzzlehttp on 1.x branch... |
going to upgrade a 1.14 to fix this?? |
Probably ... |
|
Could someone push this to 2.x branch? |
Since 2.x is not released, why not use the 2.0.0-beta? I tried it and it seems to work |
I know it's a duplicate but this includes also Symfony 6