chore: run go mod tidy specifying Go 1.21 to resolve CVE #288
Conversation
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
- 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`
| 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 |
| @LyricTian I think we need this to put the JWT CVE issue completely to rest. |
pete-woods changed the title go mod tidy specifying Go 1.21go mod tidy specifying Go 1.21 pete-woods changed the title go mod tidy specifying Go 1.21go mod tidy specifying Go 1.21 pete-woods changed the title go mod tidy specifying Go 1.21go mod tidy specifying Go 1.21 to resolve CVE 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
1.21go: github.com/golang-jwt/jwt/v5@v5.3.0 requires go@1.21, but 1.13 is requested