Skip to content

ci: add staticcheck and govulncheck to CI #71

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.

Sign up for GitHub

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

Open
leno23 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

ci: add staticcheck and govulncheck to CI #71

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,3 +28,9 @@ jobs:

- name: go test
run: go test -race ./...

- uses: dominikh/staticcheck-action@v1
with:
version: latest

- uses: golang/govulncheck-action@v1
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Scan the same Go version that gets released

When this step is left with no inputs, golang/govulncheck-action installs and scans with its default stable Go toolchain, while this workflow's earlier build/test and the release workflow both use go-version-file: go.mod (which is go 1.20). In any release built with the module-pinned toolchain, standard-library vulnerabilities that affect Go 1.20 can be missed because govulncheck is evaluating the latest stable stdlib instead of the one used for the binary; pass go-version-file: go.mod (and usually repo-checkout: false) so the vuln scan matches the artifact being shipped.

Useful? React with 👍 / 👎.