-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump faraday version from 0.12 to 1.0 #73
Conversation
This is currently failing:
Looks like |
4c5f644
to
8ef196e
Compare
8ef196e
to
cd7864f
Compare
@Lewuathe thanks for releasing tiny-presto. Now this is ready to be reviewed too! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have little experience in this codebase, but the change looks both simple and good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me though, why CI didn't run for this pull request? 🤔 Approval for the first-time contributor might be necessary but I don't see an Approve button...
Anyway, let me merge this and will see how CI works on master. Thanks for your contribution! |
Trino 1.0.2 includes some Faraday compatibility changes: treasure-data#73 treasure-data#75 But neither of those changes make the gem incompatible with Faraday 0.6.6. This commit relaxes the version so we can upgrade Presto and Faraday independently. Once we are on Faraday 1.x we can go back to the official release of this gem.
This commit applies the change from treasure-data#73 This will allow us to upgrade presto-client separately from upgrading Faraday. Once we are on Faraday v1.0 we can upgrade directly to trino-client v1.0.2 without issue.
This commit applies the change from treasure-data#73 This will allow us to upgrade presto-client separately from upgrading Faraday. Once we are on Faraday v1.0 we can upgrade directly to trino-client v1.0.2 without issue.
Purpose
resolves: #65
Currently the gem trino-client depends on Faraday 0.12. If a project uses the lastest version of Faraday (1.7) and introduces trino-client, it needs to have the Faraday gem downgraded.
Overview
Checklist
Created tests which fail without the change (if possible)Extended the README / documentation, if necessary