Update gosec2 dependency to a tagged version (v2.3.0) #1079
Conversation
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
When raising golangci#1062 I noted that the gosec dependency had been upgraded to v2, but needed to be pulled from `master` due to some issues with the v2.2.0 tagged release. That was tracked in securego/gosec#470. They've since cut v2.3.0, so let's update to that tagged release before we release a new version of golangci-lint.
|
@jirfag I assume we'll want this before v1.27.0. |
|
thank you |
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.
When raising #1062 I noted that the gosec dependency had been upgraded to v2,
but needed to be pulled from
masterdue to some issues with the v2.2.0 taggedrelease. That was tracked in securego/gosec#470.
They've since cut v2.3.0, so let's update to that tagged release before we
release a new version of golangci-lint.