-
Notifications
You must be signed in to change notification settings - Fork 73
THREESCALE-15318: Update Faraday dependency for enhanced query parameter handling #4330
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
Changes from all commits
b76cdec
ef88e9b
5783363
71d10ba
05be635
c79e8f3
4b520b7
4d8c766
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -43,7 +43,7 @@ gem 'sorted_set', '~> 1.0' | |
| gem 'i18n' | ||
|
|
||
| # Apisonator client | ||
| gem 'pisoni', '~> 1.30' | ||
| gem 'pisoni', '~> 1.31' | ||
|
|
||
| gem '3scale_time_range', '0.0.6' | ||
|
|
||
|
|
@@ -73,14 +73,26 @@ gem 'formtastic', '~> 5.0' | |
| gem 'htmlentities', '~>4.3', '>= 4.3.4' | ||
| gem 'json', '~> 2.7', '>= 2.7.1' | ||
| gem 'responders', '~> 3.2' # For respond_with support | ||
| # uri >= 1.0.0 switched the default parser from RFC2396 to RFC3986 (ruby/uri#107), | ||
| # removed URI::DEFAULT_PARSER, dropped URI.decode, and the RFC3986 parser has no | ||
| # `registry` component. We rely on all of these across models (Proxy, ProxyRule, | ||
| # WebHook, AuthenticationProvider) and controllers. Upgrading is worthwhile but | ||
| # requires careful inspection of every call-site and should be deployed/tested | ||
| # separately from the Faraday update. | ||
| gem 'uri', '< 1.0.0' | ||
|
|
||
| gem 'mysql2', '~> 0.5.3' | ||
|
|
||
| gem '3scale_client', '~> 2.11', require: false | ||
| gem 'analytics-ruby', require: false | ||
|
|
||
| # connection_pool 3.0 changed `#with` from positional to keyword-only args, | ||
| # breaking redis-client 0.22.2 (pinned by hiredis-client). Upgrading | ||
| # hiredis-client + redis-client to >= 0.26.3 would resolve this; until then | ||
| # keep connection_pool on 2.x. | ||
| gem 'connection_pool', '~> 2.2', '< 3' | ||
| gem 'dalli' | ||
| gem 'faraday', '~> 2.0', '<= 2.9' | ||
| gem 'faraday', '~> 2.0', '>= 2.14.3' | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't we limit range to 2.x?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The |
||
| gem 'mimemagic', '~> 0.3.10' | ||
| gem 'nokogiri', '~> 1.18.9', force_ruby_platform: true | ||
| gem 'secure_headers', '~> 6.3.0' | ||
|
|
||
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.
What if you just remove this and leave the reference to
connection_poolun the lockfile untouched? I don't like the idea of adding dependencies to our Gemfile when they are not our dependenciesThere 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.
Then the next
bundle installmay bring it back. I'd rather put a comment unless you give me a better alternative.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.
Fine for me