updating dependencies, addressing compiler warnings #53
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.
This PR is intended to update dependencies and address compiler warnings raised in newer versions of Elixir (1.11+)
With the shift to Elixir 1.11 and OTP 23 and above, dependencies expressly called on in an application that are not either a) included in the
:extra_applications
config of an app or b) listed in the app's dependencies will throw a compiler warning about implicit runtime dependencies. Since the:crypto
module is built into Erlang, this should be added to the extra applications configuration to address this issue going forward.I've also modified the version key based on the small size of the proposed change and my own take on semver but feel free to suggest a different version number change that you prefer.
Thanks so much!