Joel Sing <j...@sing.id.au> writes: > On 25-01-15 09:27:46, Kirill A. Korinsky wrote: >> On Wed, 15 Jan 2025 09:05:51 +0100, >> Joel Sing <j...@sing.id.au> wrote: >> > >> > Thanks, but no. I've held off on an update since various TLS tests >> > have been failing since the 1st of January 2025, plus Go 1.23.5 is >> > being released ~tomorrow: >> > >> > https://groups.google.com/g/golang-announce/c/DDJpfG1jV30 >> > >> > If we were going to update to Go 1.23.4 then we would also need the >> > backport of the TLS expiry fix: >> > >> > https://go.dev/cl/640315 >> > >> > Saying that the tests are running the same way before and after is just >> > ignoring the fact that they're broken and that a large number of tests >> > are not getting run at all, which is less than ideal. >> > >> > I'll bump to Go 1.23.5 once it becomes available. >> > >> >> Thanks, it's clear. >> >> The only reason why I had done it, because docker-compose needs 1.23.4 > > That's pretty strange/specific - is there a particular bug fix > that they need?
I'm not sure they need anything, but I don't really know docker-compose. I had the same issue with sysutils/chezmoi. I think they just bump go.mod. Or it may be the tooling doing the bump to whatever version the dev (or CI pipeline) is using.
