-
Notifications
You must be signed in to change notification settings - Fork 81
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
[7.17](backport #1978) Update to Go 1.18.7. #2009
Conversation
(cherry picked from commit 0b36872) # Conflicts: # .go-version
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
|
This pull request has not been merged yet. Could you please review and merge it @cmacknz? 🙏 |
1 similar comment
This pull request has not been merged yet. Could you please review and merge it @cmacknz? 🙏 |
This pull request has not been merged yet. Could you please review and merge it @cmacknz? 🙏 |
2 similar comments
This pull request has not been merged yet. Could you please review and merge it @cmacknz? 🙏 |
This pull request has not been merged yet. Could you please review and merge it @cmacknz? 🙏 |
I originally tried making this change assuming it was easy, but then ran into a collection of build errors and got distracted. We should follow through with this update to ensure fleet-server on 7.17 has the latest Go security patches. I am going to pre-emptively assign this to @michel-laterman since it is unlikely that I will have time for it before 7.17.8 is released. |
This pull request has not been merged yet. Could you please review and merge it @michel-laterman? 🙏 |
Closing, duplicate of #2101 |
This is an automatic backport of pull request #1978 done by Mergify.
Cherry-pick of 0b36872 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com