chore(deps): upgrade to latest go1.25.3 #3244
Conversation
Signed-off-by: Jan Larwig <jan@larwig.com>
2124b14 to
371ef8d
Compare
| module github.com/oauth2-proxy/oauth2-proxy/v7 | ||
|
|
||
| go 1.24.6 | ||
| go 1.25.3 |
There was a problem hiding this comment.
Nit, it's best practice to pin to the .0 in the go.mod. I'd like to see this validated by a linter at some point (I have this as a todo for many projects) so will work out a good way to bring this here once I've worked it out there
There was a problem hiding this comment.
@JoelSpeed but when I tested the binary was built with exactly 1.25.0 and not with the latest available patch version 🤔
There was a problem hiding this comment.
go 1.25 without the patch .0 might work
There was a problem hiding this comment.
Oh really? 🤔 That's interesting
I've been told by the a Go security team member that this number should not be non-zero. The go.mod is supposed to specify the minimum version, not a specific version
Is some other part of our build tooling tied to this number for any reason?
Description
Upgrade to latest go1.25.3
How Has This Been Tested?
Regression test, build, linting and unit tests.
Checklist: