Downgrade Go version requirement to 1.20 #17
Merged
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
As part of the upgrade to Go 1.21, the Go toolchain now requires the `go` directive to match the maximum Go version in use in dependencies. This leads to any transitive dependency on this library to result in a requirement of the consuming project moving to Go 1.21. Although in a lot of cases this may not be as problematic, it forces consumers to migrate, which we don't need to do in this case.
This was referenced Sep 4, 2023
kataras
approved these changes
Sep 8, 2023
|
Thank you! 1.20 is still supported by the Go team so for now will be getting security updates too ☺ |
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.
As part of the upgrade to Go 1.21, the Go toolchain now requires the
godirective to match the maximum Go version in use in dependencies.This leads to any transitive dependency on this library to result in a
requirement of the consuming project moving to Go 1.21.
Although in a lot of cases this may not be as problematic, it forces
consumers to migrate, which we don't need to do in this case.
As discussed in oapi-codegen/oapi-codegen#1221 and related change in gofiber/fiber#2614. See also golang/go#62409