-
Notifications
You must be signed in to change notification settings - Fork 444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go 1.17.8 #4560
Go 1.17.8 #4560
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/fleet-dm/fleet/EB7EG7f6HQTkDG7Sz1QndLC9rBAt |
Let's also update
(I wonder if there's a way to define this once for all workflows, no need to tackle that on this PR, just a thought.) |
Bumping minimum version in a few more files
Updated as per @lucasmrod's comments! |
Thanks @GuillaumeRoss! While we are at it, we just had our backend call a few minutes ago and were discussing upgrading straight to 1.18 (released yesterday). Could we try that on this PR? (alternatively we merge this one and I can create a new one for 1.18). Looks like the issue is fixed in 1.18 too (golang/go#51112). |
@lucasmrod Let's merge this one, then immediately create a new one. That way if we have any troubleshooting on 1.18 we will not hold back the fixing of a vulnerability (even though it's minor). OK with you? |
* Go 1.17.8 * Enforcing go minimum 1.17.8 Bumping minimum version in a few more files
@zwass just to save you a bit of time on #4462 I went ahead and commited this. I am unsure why goreleaser-orbit only had 1.17 specified - if you feel like this is all good feel free to schedule this change when it makes sense, the vulnerability before 1.17.8 is not major at all for us.