chore: Accommodate jwt's minor and patch updates #630
Merged
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.
Current specification in gemspec pins the jwt version to the latest released one, consequently setting an obstacle where users have to wait until twilio-ruby modifies gemspec and releases it in order to update jwt.
Although I truly appreciate that you are constantly updating this library, I think it would be better if it accommodates updating jwt independent of twilio-ruby.
Also this change will
As a reference which might help, oauth2 gem relies on jwt in this manner: https://rubygems.org/gems/oauth2
Checklist
If you have questions, please file a support ticket, or create a GitHub Issue in this repository.