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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ jwt (2.7.1 → 2.8.0) · Repo · Changelog
Release Notes
2.8.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 32 commits:
Version 2.8.0
Adjust to changed exception message
Algorithm cleanup.
Deprecate the loose base64 decoding.
Relocate changelog entry
Relocate into constant
Update changelog
Remove unused method
Apply Rubocop
Add a good explainer
Fix the bug
Add a failing test
Changelog entry
Add missing RSpec module references to initial describe calls
Move all specs under the jwt folder
Improvements for key handling in specs:
Fix requires for x5c_key_finder
Run CI on Ruby 3.3
Fix example code of x5c header in README
Update CHANGELOG
Add type check to key_base '<=>' operator
Add type check to key_base '==' operator
Remove rubocop exact version dependency from appraisal gemfiles
Do not specify the desired rubocop version on older rubies
Update to rubocop 1.56
Pull request template
Remove duplicate changelog header
Prepare changelog for current iteration
[spec] rspec to test that strings containing exp/nbf/iat are not
verify whether the payload responds to key? when veriying claims
follow rubocop standards
fix signature has expired error if payload is a string
🆕 base64 (added, 0.2.0)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands