Update dependency on api-auth
#18
Open
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.

Add pry to Gemfile
Add pry to Gemfile so you can
bundle exec rspec(if you don'tbundle exec, you could get random versions of the gems, but if you do, then it can't loadpryas it's not specified as a development dependency)Update ApiAuth to
~> 2.0ApiAuth v1 has insecure defaults and uses deprecated Faraday features which lead to test spam. This bumps it to ~>2.0, because that allows for versions which use Faraday correctly, and fixes the security vulnerabilities.
Example of the Faraday deprecation warning from Mifiel's test suite:
Co-authored-by: Angel Malavar angel.malavar@gmail.com