Context
We've had a number of request to upgrade the "golang.org/x/crypto" library recently. While the APIs we use in that module are still not impacted by any CVEs, many users seem to get CVE warnings because they're not using govulncheck.
We should consider upgrading "golang.org/x/crypto" to a newer version and bumping the min supported Go version.
Questions:
- Is there a version of "golang.org/x/crypto" that resolves CVEs and also requires a version of Go that we're OK with requiring?
Definition of done
- Bump version of "golang.org/x/crypto" to v0.52.0
- Bump min Go version to "1.25.0"
- Update version list in compile_check_test.go to remove 1.19 thru 1.24
- Update the Taskfile min Go version build check here to use 1.25 instead of 1.19
- Update README.md and AGENTS.md to reflect that min Go version is 1.25
Pitfalls
The previous min version was 1.19 (released Aug 2022), so 1.25 (released Aug 2025) is a significant jump. It's possible it will require some users to upgrade Go.
- related to
-
GODRIVER-3907 Bump minimum Go version to 1.21 or higher
-
- Backlog
-
-
GODRIVER-3552 Bump the minimum Go Version to 1.21
-
- Closed
-