https://flyte.org logo
Join Slack
Powered by
:wave: Any updates on getting a release cut that b...
# contribute
g
👋 Any updates on getting a release cut that bumps to Go 1.23? The work has landed and we could use an interim commit for flyteidl internally, but preferring to stick to tags / releases - thanks!
c
Looks like it should be included in the v1.16.0 release which is in progress
👍 1
a
@gorgeous-waitress-5026 as Jason said, this landed in 1.16.0 https://github.com/flyteorg/flyte/releases/tag/v1.16.0
g
Working through integrating / upgrading Domino codebase now Any chance that we can get a flytectl version cut as well? I don't think much has materially changed, aside from vuln remediation (which is what I'm primarily interested in)
Going to revive this thread now for Go 1.24 - have things being going well in prod for you with 1.24 @clean-glass-36808?
c
I still haven't landed Go 1.24 in our environment because of other commitments but I can try while things are slow on this break
I really want to get Flyte onto Go 1.25 for the MAXPROCs improvements
g
Yeah, that's a very very good reason to get up to Go 1.25 -- we've been migrating our internal projects over
c
I just filed a pull request internally. Will probably be able to soak test the changes next week and get some signal
g
That would be fantastic - thanks!
As we prep for another release on our side, of course the vuln scanners are not happy with Go 1.23 🙂
c
Just landed it in our non-production environment
🙏 1
Merged
Will open up a PR for 1.25 in a bit
g
woohoo
c
I have a draft PR for Go 1.25 here: https://github.com/flyteorg/flyte/pull/6771 It was a little gnarlier than i thought it would be
g
Yeah, golangci-lint v2 ended up being some work for projects I ported over from 1.24 as well
4 Views
Open in Slack
PreviousNext
Powered by