Skip to content

ci: move Trivy scan to periodic workflow - #1651

Open
ZohebShaikh wants to merge 1 commit into
mainfrom
trivy
Open

ci: move Trivy scan to periodic workflow#1651
ZohebShaikh wants to merge 1 commit into
mainfrom
trivy

Conversation

@ZohebShaikh

Copy link
Copy Markdown
Contributor

Summary

  • Move the Trivy container vulnerability scan out of the per-PR/push container build (_container.yml) into its own workflow (trivy.yml)
  • Trivy now runs weekly on a schedule (matching periodic.yml's cadence) and via workflow_dispatch, instead of on every push/PR

Test plan

  • Built the container from main locally and confirmed the CLI works
  • Ran Trivy against that image and confirmed it correctly reports vulnerabilities (found existing HIGH findings in msgpack and a bundled pebble binary, unrelated to this change)
  • Confirm the new trivy.yml workflow runs successfully via workflow_dispatch on GitHub

🤖 Generated with Claude Code

Scanning the container image on every push/PR added time to a path that runs on every commit. Trivy now runs on its own weekly schedule (matching periodic.yml's cadence) and via workflow_dispatch, building the image from the checked-out ref and scanning it independently of the PR build.

Verified by building the container from main locally and running Trivy against it, which correctly surfaced existing HIGH vulnerabilities.

Claude-Session: https://claude.ai/code/session_01AV8asKUKbiS7A5Fz7YWqZy

@ZohebShaikh
ZohebShaikh requested a review from a team as a code owner September 2, 2026 12:06
@codecov

codecov Bot commented Sep 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.34%. Comparing base (e549cd0) to head (5f8d358).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1651   +/-   ##
=======================================
  Coverage   96.34%   96.34%           
=======================================
  Files          46       46           
  Lines        3666     3666           
=======================================
  Hits         3532     3532           
  Misses        134      134           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ZohebShaikh

Copy link
Copy Markdown
Contributor Author

Ran the workflow in my fork manually.
Add it is running

Scanning the container image on every push/PR added time to a path
that runs on every commit. Trivy now runs as a job in periodic.yml,
on the same weekly schedule and workflow_dispatch as the rest of the
periodic checks, building the image from the checked-out ref and
scanning it independently of the PR build. Pin the trivy-action's
version input to v0.74.0 so the scanned trivy version doesn't shift
under us on a future trivy-action bump.

Verified by building the container from main locally and running
Trivy against it, which correctly surfaced existing HIGH
vulnerabilities.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AV8asKUKbiS7A5Fz7YWqZy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant