Dependencies: Upgrading modules 2024-02 #319
Open
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
vtopc
approved these changes
Sep 26, 2024
|
@ryanlelek, sorry, I didn't merge it in time, and now there are some conflicts. Could you fix them? |
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.
What:
Dependency upgrades
Why:
Existing dependencies are a bit outdated. When this happens, Go tends to use the lowest compatible version. So, lower dependencies here can effectively downgrade some modules of the projects it's included in.
Extra Discussion:
Completely understandable to keep the minimum Go version at 1.13 for compatibility. With the recent release of Go v1.22, the official support is v1.21+ Source.
Starting to slowly bump up the minimum Go version might encourage projects to use an officially supported version