ci(publish): unify image scanning across published images#4306
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📜 Recent review details⏰ Context from checks skipped due to timeout. (6)
🔇 Additional comments (3)
WalkthroughThe workflows now expose published image version and repository outputs from the worker build. The publish workflow invokes the shared Trivy image scanner for both webapp and supervisor images. The Trivy workflow has been generalized from webapp-specific usage, including its name, concurrency key, report filename, and job summary output. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
Run the shared Trivy image scan on every published image through a single reusable workflow.
Changes
trivy-image-webapp.yml->trivy-image.yml) - it was already parameterised byimage-ref; only the run-summary label was image-specific.publish-worker-v4.yml: exposeversion+image_repoas workflow outputs (single-entry matrix, so unambiguous).publish.yml: run the shared scan from each publish job (scan-webapp,scan-supervisor).Report-only (writes a table to the run summary), OS packages only (
vuln-type: os- library deps stay with Dependabot), never blocks the publish.