Skip to content

ci(scout): scan the image once it is published, and gate on that scan - #74

Merged
maksimtech merged 1 commit into
mainfrom
ci/scan-after-publish
Oct 24, 2026
Merged

maksimtech merged 1 commit into
mainfrom
ci/scan-after-publish

Conversation

@maksimtech

Copy link
Copy Markdown
Owner

Docker Scout scans the published latest image but ran only on a push to main, weekly or by hand: after the certifi release the Security Posture gate stayed red on the replaced image until both were dispatched by hand.

  • docker-scout.yml: also on workflow_run of the workflow that pushes the image, completed; the job runs only when that run succeeded.
  • security-posture.yml: also on workflow_run of Docker Scout CVE Scan; with workflow_run, github.ref is refs/heads/main.
  • docs/nis2-compliance.md: the Docker Scout row says it runs on every image build.

TDD: tests/test_scan_after_publish.py (the triggers, that the named workflows exist, no scan after a failed push, dispatch and schedule kept, the document) failed before the change. Full suite: 2263 passed, 4 skipped in 117.89s (0:01:57). Same change as maksimtech/mailradar#67.

🤖 Generated with Claude Code

Docker Scout reads the published latest image from Docker Hub but ran only
on a push to main, weekly or by hand. After the certifi release the
Security Posture gate stayed red on the replaced image until Docker Scout
and the gate were dispatched by hand. docker-scout.yml now follows the
workflow that pushes the image (workflow_run, successful runs only) and
security-posture.yml follows "Docker Scout CVE Scan"; the NIS2 document
says the scan runs on every image build. Same change as
maksimtech/mailradar#67.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@codecov

codecov Bot commented Oct 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@codspeed

codspeed Bot commented Oct 24, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

1 warning

⚠️ 11 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 17 untouched benchmarks


Comparing ci/scan-after-publish (d99a7b1) with main (8443b93)

Open in CodSpeed

@sonarqubecloud

Copy link
Copy Markdown

@maksimtech
maksimtech merged commit f5e5d01 into main Oct 24, 2026
25 checks passed
@maksimtech
maksimtech deleted the ci/scan-after-publish branch October 24, 2026 17:22
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