Skip to content

ops(security): scan main on push too, so post-fix scans clear stale alerts#148

Merged
amavashev merged 1 commit into
mainfrom
ops/scan-on-main-push
May 3, 2026
Merged

ops(security): scan main on push too, so post-fix scans clear stale alerts#148
amavashev merged 1 commit into
mainfrom
ops/scan-on-main-push

Conversation

@amavashev
Copy link
Copy Markdown
Collaborator

Adds push: branches: [main] trigger to pr-container-scan.yml so Trivy re-scans after every fix merge — closing the stale-alerts gap that required PR #57 to manually nudge events.

Same change applied across cycles-server-admin, cycles-server-events, cycles-dashboard for consistency.

…lerts

Trivy alerts on the main-branch alert track only auto-close when a SARIF
scan publishes against refs/heads/main with the same (workflow, job,
category) tuple. Currently pr-container-scan.yml only triggers on
pull_request, so scans always upload against PR refs — main-track alerts
go stale after every fix merge.

Concrete impact: cycles-server-events had 13 stale gnutls alerts after
PR #54 (the gnutls fix) merged. Required a no-op Dockerfile-comment PR
(#57) to retrigger the scan and finally clear them.

Fix: add 'push: branches: [main]' trigger with the same paths filter.
Now every fix-merge to main re-scans and updates the alert track.

Side effect: image tag template changed from 'pr-N' to 'scan-{N or sha}'
so it's defined for both event types. Image is local-only (load:true,
push:false) so the tag value doesn't matter to anything downstream.
@amavashev amavashev enabled auto-merge (squash) May 3, 2026 11:04
@amavashev amavashev merged commit 5467921 into main May 3, 2026
7 checks passed
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