chore: upgrade Go version to 1.21 and update modules #192
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
but, it includes some breaking changes for supported jwt claims and errors
MatsuoTakuro
requested review from
zhongdalu-trechina,
SunJinping-TRE-C,
tanvir-retailai and
ZhaoYuRetailAI
zhongdalu-trechina
approved these changes
Jun 24, 2024
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.
This PR includes a breaking change for supported jwt claims and errors according to golang-jwt's Migration Guide (v5.0.0)
Claimsinterface.StandardClaimsstruct doesn't implement it and has been already removed now in v5. Instead, you can embedRegisteredClaimsstruct into your custom claims.ErrJWTokenInvalidandErrJWTokenExpiredsentinel errors that are underlying an error returned byhelper.DecodeJWT(). These errors wraps original joined errors provided bygolang-jwt.