Skip to content

ci: pin Trivy binary version to v0.70.0#681

Merged
david-waltermire merged 1 commit intometaschema-framework:developfrom
david-waltermire:fix/trivy-version-pin
Apr 19, 2026
Merged

ci: pin Trivy binary version to v0.70.0#681
david-waltermire merged 1 commit intometaschema-framework:developfrom
david-waltermire:fix/trivy-version-pin

Conversation

@david-waltermire
Copy link
Copy Markdown
Contributor

@david-waltermire david-waltermire commented Apr 19, 2026

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

  • CI's Trivy step installs successfully and produces `trivy-results.sarif`.

Summary by CodeRabbit

  • Chores
    • Updated build workflow configuration to specify a fixed version for security scanning, ensuring consistent and reproducible builds across environments.

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.
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 19, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 58749d2d-3f56-4a77-b270-02caff21fdaa

📥 Commits

Reviewing files that changed from the base of the PR and between 22bc468 and 4d14a47.

📒 Files selected for processing (1)
  • .github/workflows/build.yml

📝 Walkthrough

Walkthrough

The pull request pins the Trivy security scanning action to version v0.70.0 in the GitHub Actions workflow build configuration. Previously, the action relied on auto-detection of the latest version. No other scanning logic or workflow steps are modified.

Changes

Cohort / File(s) Summary
Trivy Version Pinning
.github/workflows/build.yml
Added explicit version pin version: 'v0.70.0' to the aquasecurity/trivy-action step, replacing reliance on auto-detected latest version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 A version is pinned, oh what delight! \
No drifting to newest, we hold it tight. \
v0.70.0 stands strong and true, \
Security locked in, tried and through! 🔒✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title clearly and concisely describes the main change: pinning the Trivy binary version to v0.70.0 in CI configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@david-waltermire david-waltermire merged commit 4d4e6c2 into metaschema-framework:develop Apr 19, 2026
5 of 6 checks passed
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