ci: pin Trivy binary version to v0.70.0#681
Conversation
The trivy-action pinned in build.yml delegates binary installation to setup-trivy, which auto-detects the latest Trivy tag. That currently resolves to v0.69.1, for which no Linux-64bit binary was published (the release download returns HTTP 404). setup-trivy then fails the scan step with exit code 1, blocking CI on most PRs. Explicitly pin to v0.70.0 so the installer targets a known-good binary. Dependabot will continue to surface Trivy action updates, which can bump this pin in lockstep when appropriate.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request pins the Trivy security scanning action to version Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
4d4e6c2
into
metaschema-framework:develop
Summary
Pin the Trivy binary version to `v0.70.0` to fix flaky CI failures on the "Run Trivy security scanner" step.
Root cause
`aquasecurity/trivy-action` delegates binary installation to `aquasecurity/setup-trivy`. When no `version` input is provided, setup-trivy auto-detects the latest Trivy tag. It currently resolves `v0.69.1`, but no `trivy_0.69.1_Linux-64bit.tar.gz` was ever published — the download URL returns HTTP 404. The installer fails silently with exit code 1, blocking CI on most PRs (e.g. #672, #679).
Fix
Explicitly set `version: v0.70.0`, which has published binaries. Dependabot will continue to surface action updates and can bump this pin in lockstep when appropriate.
Test Plan
Summary by CodeRabbit