With Go 1.22 EOL several months ago (<https://endo...
# contribute
g
With Go 1.22 EOL several months ago (https://endoflife.date/go) and not receiving security updates any more, would it be possible to prioritize upgrading Flyte to build on Go 1.23 (or ideally 1.24). The PR got started at https://github.com/flyteorg/flyte/pull/6249 a while back by @clean-glass-36808 but stalled out due to mockery issues. Our internal scanners are starting to flag things more frequently in the Flyte stack (including flytectl), so it's becoming a larger issue on our side. I can lend a hand too -- I just want to make sure the PR can be reviewed / merged promptly as I think there's going to be a potential for merge conflicts if other PRs get priority.
c
FWIW, we've been using the PR in our fork since February in production
g
Ok cool -- had a feeling it was working fine. So we basically need to get things merged in the OSS repos and get the releases cut
Did you solve the mockery issue in the Union fork?
c
I don't work at Union. I work at a company just using/forking OSS flyte.
From what I understand there was some concern about either updating mockery or updating go and thats why @high-accountant-32689 wanted to separate those units of work into different PRs but they seem to be tightly coupled.
g
Oh oh sorry - got my lines crossed. I thought you were on the core team there 🙂
f
haha hey @gorgeous-waitress-5026 thank you for bringing this up
we will also try to upgrade it