CI Failure with Trunk 1.22.7 – Trivy Exiting with Code 1

[vtsachev]

A user has reported an issue where Trunk 1.22.7 fails in CI but does not reproduce locally. The failure appears intermittent, sometimes resolving with a rebase.

Reported Behavior

• Running ./trunk check --ci --ci-progress --github-commit <commit_hash> --github-annotate in CI results in a failure.
• The output includes:
  • Trivy exiting with exit_code=1
  • Fatal error in Trivy stderr:

FATAL Fatal error fs scan error: scan error: scan failed: failed analysis: post analysis error: post analysis error: helm scan error: scan config error: failed to init rego scanner: failed to load rego checks from [.]: range error: stat /home/gradle/.cache/trunk/repos/zzz/results/trivy/policy/content/policies/cloud/policies/aws/cloudwatch/require_console_login_failure_alarm.rego: no such file or directory

• No issues detected, but Trivy failure recorded
• Issue appears randomly across multiple PRs.

Version
• Trunk CLI: 1.22.7
• Trivy Version: 0.58.2