Upgrade to Omnipay v3 #6
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey, long time no see :)
This PR updates the package from Omnipay v2 to Omnipay v3. There is almost no changes except PayoutRequest: Omnipay moved to their own interface of an HTTP Client and it does not support that weird Webmoney logic with self-signed SSL certificate. That's why I've used Guzzle directly there.
I suggest you to tag a
2.0release out of currentmasterbranch, then push it as2.0branch for the history.Then merge this PR into
masterbranch and tag a3.0request.If you don't have eager to do it, you can give me the contributor permissions and I'll finish it.
Thanks!