Skip to content

chore: run go mod tidy specifying Go 1.21 to resolve CVE - #288

Merged
LyricTian merged 1 commit into
go-oauth2:masterfrom
pete-woods:cve-jwt
Aug 20, 2025
Merged

chore: run go mod tidy specifying Go 1.21 to resolve CVE#288
LyricTian merged 1 commit into
go-oauth2:masterfrom
pete-woods:cve-jwt

Conversation

@pete-woods

@pete-woods pete-woods commented Aug 18, 2025

Copy link
Copy Markdown
Contributor
  • Seems the JWT v5 dependency actually requires 1.21
  • go: github.com/golang-jwt/jwt/v5@v5.3.0 requires go@1.21, but 1.13 is requested

- See the JWT dependency now requires `1.21`
- `go: github.com/golang-jwt/jwt/v5@v5.3.0 requires go@1.21, but 1.17 is requested`
@pete-woods

pete-woods commented Aug 18, 2025

Copy link
Copy Markdown
Contributor Author

I've also created a second PR we could look at once this PR is merged that bootstraps a GHA workflow, that would help avoid an invalid go.mod in future.

@pete-woods

Copy link
Copy Markdown
Contributor Author

@LyricTian I think we need this to put the JWT CVE issue completely to rest.

@pete-woods pete-woods changed the title Run go mod tidy specifying Go 1.21 chrome: run go mod tidy specifying Go 1.21 Aug 18, 2025
@pete-woods pete-woods changed the title chrome: run go mod tidy specifying Go 1.21 chore: run go mod tidy specifying Go 1.21 Aug 18, 2025
@pete-woods pete-woods changed the title chore: run go mod tidy specifying Go 1.21 chore: run go mod tidy specifying Go 1.21 to resolve CVE Aug 19, 2025
@LyricTian
LyricTian merged commit c1329d9 into go-oauth2:master Aug 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants