ci: move govulncheck to weekly cron#348
Merged
Merged
Conversation
govulncheck ran on every PR and push to main. Vulnerability advisories don't land that frequently, so per-PR runs mostly burn runner minutes detecting nothing new. Moving to a weekly schedule (Monday 06:00 UTC) plus workflow_dispatch keeps coverage with a fraction of the cost. The govulncheck.yml workflow is a verbatim extract of the previous ci.yml job, including the GO-2026-4887/4883 Docker daemon false- positive suppression.
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.
Summary
Test plan