-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump common and fix Chain Writer naming #328
Conversation
Did CI get stuck? |
Oh, or are the required CI jobs hard-coded with a Go version |
seems like it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I believe CI will pass after #339 is merged.
gosec: | ||
# TODO - remove this and fix linter complaint | ||
excludes: | ||
- G115 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How many were there? It would be a little better to mark them directly as //nolint:gosec // G115 ....
if it's not too much trouble.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
10+
|
||
ensure_golangcilint_1_59: | ||
@golangci-lint --version | grep -q '1.59' || (echo "Please use golangci-lint 1.59" && exit 1) | ||
ensure_golangcilint_1_62_2: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this pattern serve a purpose? Or could we drop it?
ensure_golangcilint_1_62_2: | |
ensure_golangcilint_version: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should drop it
|
core ref: fa346afd62ef6f6f97b18ddae4eee2298ebc5001