Add govulncheck & staticcheck to CI, update action dependencies#221
Merged
Conversation
Rather than use Dependabot and get churn notifications for updates that aren't important for this repo, let's use govulncheck.
Linting our tooling should be separate from linting the vector data with that tooling.
FiloSottile
approved these changes
Feb 20, 2026
Member
Author
This is done. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
An alternative to getting low-value update PRs like #220 inspired by the Geomys standard of care. I've opted not to include a job testing the latest version of dependencies, it isn't obvious to me it's important for this repo.
If we merge this, I'll ask the C2SP folks with admin access to disable Dependabot for this repo.