Merged
Conversation
Member
|
Is there any reason we're not using Go 1.17 yet? Go 1.16 will be deprecated in just 2 months. |
Contributor
Author
|
Mostly just timing. We didn't get #8550 fixed in time for 0.11, and wanted to keep v0.11 and 0.12 as similar as possible. It would have been nice to know we'd get this failure soon after 1.17 came out so we'd have more time to release it, but since we're only running CI against one version at the moment this kind of thing shouldn't be too surprising. |
5395919 to
b4814fe
Compare
guseggert
approved these changes
Dec 13, 2021
Closed
Closed
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Waiting on CircleCI-Public/cimg-go#142