feat: migrate to jwt v5 #152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CoreFloDev
force-pushed
the
feat/migrate-to-jwtv5
branch
3 times, most recently
from
dc5005a
to
66e283d
Compare
Signed-off-by: CoreFloDev <[email protected]> Signed-off-by: “CoreFloDev” <“[email protected]”>
CoreFloDev
force-pushed
the
feat/migrate-to-jwtv5
branch
from
66e283d
to
ffd369f
Compare
|
I did the required changes for the DCO, it doesn't seems to work I don't get why. Anyway, this PR should close #136 as well |
|
Nice! I don't have merge right so I let you do it 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
I did the migration do jwtv5 there wasn't much to do as the repo doesn't use methods that have been refactored
Have a look at https://github.com/golang-jwt/jwt/releases/tag/v5.0.0 if you want more details on the changes
Thanks