Bump go.mod to 1.18 #115
Merged
Bump go.mod to 1.18 #115
Conversation
This file contains 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
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.
This is in attempt to align the compatible Go version with
terraform-execand some other libraries in our ecosystem, to try to help the supply chain CVE scanners be more accurate.I am not sure it will actually help, but the common support model in our HashiCorp libraries is two last major Go versions anyway, so this shouldn't harm and shouldn't come as a surprise to consumers.
One example I'm hoping to shed more light on is GO-2023-1571 in
golang.org/x/net@v0.6.0whichhc-installshould not really be depending on anyway, at least not anymore. There's also hope it will make hashicorp/terraform-exec#367 redundant once we bumphc-installinterraform-execdownstream.