Upgrade dependencies, add Go 1.19 as target #82
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
Slijkhuis
force-pushed
the
upgrade-dependencies
branch
from
5ac21ee
to
7c1aa88
Compare
Slijkhuis
force-pushed
the
upgrade-dependencies
branch
from
7c1aa88
to
a3251f1
Compare
|
@jinzhu please merge |
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.
The
gopkg.in/yaml.v2dependency triggers some security warnings (CVE-2022-28948). As far as I can see there's no feasible attack surface unless the config files are user generated input. However, you never know how this library is being used in the wild.