Skip to content

Limit container image scanning to gh-* workflow images#47429

Draft
pelikhan with Copilot wants to merge 1 commit into
mainfrom
copilot/update-scanned-container-gh-containers
Draft

Limit container image scanning to gh-* workflow images#47429
pelikhan with Copilot wants to merge 1 commit into
mainfrom
copilot/update-scanned-container-gh-containers

Conversation

Copilot AI commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

The daily container image scan was sweeping every container referenced by compiled workflow manifests, including third-party MCP and example images. This change narrows the scan set to GitHub-owned gh-* images so the workflow reports on the containers we maintain.

  • Scope reduction

    • Filter manifest-derived container entries before deduplication so only images with a path component matching gh-* are included in images.json.
    • This keeps the scan focused on gh-aw and related GitHub-managed containers such as gh-aw-firewall/*, gh-aw-node, and gh-aw-mcpg.
  • Workflow behavior

    • Preserve the existing manifest extraction, pin validation, vulnerability scanning, and issue reporting flow.
    • Only the candidate image set changes; downstream scan logic remains unchanged.
  • Generated artifacts

    • Recompiled daily-squid-image-scan.lock.yml to keep the generated workflow in sync with the source workflow.
[
  .[].containers[]?
  | select(.image | test("(^|/)gh-[^/:@]+"))
]
| unique_by(.pinned_image)
| sort_by(.image)

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title Limit container image scan to gh-* workflow images Limit container image scanning to gh-* workflow images Jul 22, 2026
Copilot AI requested a review from pelikhan July 22, 2026 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants