Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

Commit

Permalink
Update faraday requirement from ~> 0.9 to >= 0.9, < 2.0 (#5)
Browse files Browse the repository at this point in the history
Updates the requirements on [faraday](https://github.com/lostisland/faraday) to permit the latest version.
- [Release notes](https://github.com/lostisland/faraday/releases)
- [Changelog](https://github.com/lostisland/faraday/blob/master/CHANGELOG.md)
- [Commits](lostisland/faraday@v0.15.4...v1.3.0)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
  • Loading branch information
dependabot[bot] authored Mar 17, 2021
1 parent 822f011 commit ddd0eac
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 3 deletions.
8 changes: 6 additions & 2 deletions Gemfile.lock
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ PATH
remote: .
specs:
cloverly (0.1.2)
faraday (~> 0.9)
faraday (>= 0.9, < 2.0)

GEM
remote: http://www.rubygems.org/
Expand All @@ -11,8 +11,11 @@ GEM
coderay (1.1.2)
diff-lcs (1.3)
dotenv (2.7.2)
faraday (0.15.4)
faraday (1.3.0)
faraday-net_http (~> 1.0)
multipart-post (>= 1.2, < 3)
ruby2_keywords
faraday-net_http (1.0.1)
ffi (1.10.0)
formatador (0.2.5)
guard (2.15.0)
Expand Down Expand Up @@ -59,6 +62,7 @@ GEM
diff-lcs (>= 1.2.0, < 2.0)
rspec-support (~> 3.8.0)
rspec-support (3.8.0)
ruby2_keywords (0.0.4)
ruby_dep (1.5.0)
shellany (0.0.1)
thor (0.20.3)
Expand Down
2 changes: 1 addition & 1 deletion cloverly.gemspec
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Gem::Specification.new do |s|
s.required_ruby_version = ">= 2.5.0"
s.required_rubygems_version = ">= 1.8.11"

s.add_dependency('faraday', '~>0.9')
s.add_dependency('faraday', '>=0.9', '<2.0')

s.add_development_dependency "rspec"
s.add_development_dependency "guard"
Expand Down

0 comments on commit ddd0eac

Please sign in to comment.