-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
fix: Security upgrade jsonwebtoken to 9.0.0 #8431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for opening this pull request!
|
Codecov ReportBase: 94.13% // Head: 94.12% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## release-5.x.x #8431 +/- ##
=================================================
- Coverage 94.13% 94.12% -0.02%
=================================================
Files 182 183 +1
Lines 13779 13776 -3
=================================================
- Hits 12971 12966 -5
- Misses 808 810 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
## [5.4.2](5.4.1...5.4.2) (2023-02-16) ### Bug Fixes * Security upgrade jsonwebtoken to 9.0.0 ([#8431](#8431)) ([2c19c2e](2c19c2e))
🎉 This change has been released in version 5.4.2 |
Pull Request
Issue
The latest JWT library prevents mocking of the decode property, which we use to determine a JWT's headers.
Closes: #8427
Approach
Add ability to mock decode
Tasks