Bump Go to 1.25.11 and migrate jwt to v5#72
Open
delize wants to merge 1 commit into
Open
Conversation
- Update CI workflows and Dockerfile to Go 1.25.11; bump the
go.mod toolchain directive to 1.25.0.
- Migrate from the unmaintained golang-jwt/jwt v3.2.2+incompatible
to golang-jwt/jwt/v5 v5.3.1. Replace *jwt.StandardClaims with
jwt.RegisteredClaims and rewrite ParseToken's expiry check to
use the new ExpiresAt field (preserves the prior "missing exp
is valid" behavior).
- Refresh golang.org/x/{image,sync,text} that came with the
toolchain bump.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
go.yml,release.yml) and the Dockerfile; bump thego.modtoolchain directive to 1.25.0.golang-jwt/jwtv3.2.2+incompatible togolang-jwt/jwt/v5v5.3.1. Replace*jwt.StandardClaimswithjwt.RegisteredClaimsand rewriteParseToken's expiry check to use the newExpiresAtfield. The prior "missing exp is treated as valid" behavior is preserved (old code passedreq=falsetoVerifyExpiresAt; new code short-circuits whenExpiresAt == nil).golang.org/x/{image,sync,text}that came along with the toolchain bump.Test plan
go build -v .succeedsgo test ./...passes locally