Update dependency gem versions #4
Open
Conversation
This file contains 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
|
Maybe we should start removing the alipay code instead? |
|
Yes we should remove alipay code. But added this PR to update the dependencies if anyone use in future |
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.
TE still have
alipay-global& alipay integration code base even though we don't use Alipay directly anymore.alipay-globalis using an old version ofrest-clientwithmime-types < 3.0Because of
mime-typesversion conflict we couldn't updatehttpartygem to the latest.So @melvrickgoh @arnvald it would be great if you can merge this
rest-clientupdate to master & release0.0.7to rubygemsAnd also I found out
fakewebgem is not supporting from Ruby 2.4 onwards - chrisk/fakeweb#57 & addedfakeweb-fias the fix. And fixed some failing tests