feat(workflows): detailed per-image scan report#47
Merged
Conversation
For each scanned tag the reusable workflow now emits a report to the run log and the job summary describing: - the image scanned and whether it was promoted or left in quarantine - every vulnerability at or above the threshold (severity, package, installed/fixed versions) - whether each finding was blocking or matched the exception list The job summary keeps the per-tag overview table and adds a collapsible per-image vulnerability detail section.
There was a problem hiding this comment.
Pull request overview
This PR enhances the reusable container scanning workflow by adding richer, human-readable reporting in both the run log and the GitHub Actions job summary, and updates the architecture docs to describe the new reporting output.
Changes:
- Add per-image run-log reporting and a collapsible per-image vulnerability detail section in the job summary.
- Include per-CVE metadata (severity, package, installed/fixed versions) with severity-ranked ordering and deduping.
- Update workflow architecture documentation to reflect the new report outputs.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
.github/workflows/_scan-image.yml |
Adds detailed per-tag console reporting and expands the job summary with per-image vulnerability details. |
docs/architecture/workflows/scan-and-promote-workflows.md |
Documents the new reporting behavior and outputs produced by the reusable scan workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Build comma-separated, Markdown-safe display variants (remaining_md, excepted_md) for the summary tables; keep the pipe-separated excepted_str only for the oras annotation - Replace `paste -sd ', '` (alternating-char delimiter) with a proper comma+space join - Relabel finding counts as "CVEs" in the run log, the <details> summary, and the overview table header (counts are unique CVE IDs) - Drop the unused `tee` to a temp file; print the report directly
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds detailed scan reporting to the reusable
_scan-image.ymlworkflow. For every scanned tag the workflow now produces a clear report of what was scanned, whether it was promoted, and the vulnerabilities found — including whether each one was blocking or covered by the exception list.What's new
Validation
bash -n, andactionlintall pass.Notes
No input or behavior changes to the gate itself — this is reporting only. Docs updated in
scan-and-promote-workflows.md.