Skip to content

Scan the published image instead of a fresh build - #78

Merged
polius merged 1 commit into
mainfrom
ci/scan-published-image
Nov 9, 2026
Merged

polius merged 1 commit into
mainfrom
ci/scan-published-image

Conversation

@polius

@polius polius commented Nov 9, 2026

Copy link
Copy Markdown
Owner

Why

The weekly scan builds the image fresh, and that build now runs apk upgrade. A fresh build therefore always has the latest Alpine fixes, so the scan passes even while the image on Docker Hub is still vulnerable, which is the case it exists to catch.

What

The workflow now scans poliuscorp/filesync:latest, the image users run, instead of building one. The checkout and build steps are gone, and the schedule and failure thresholds are unchanged.

Current state

poliuscorp/filesync:latest fails today on zlib CVE-2026-4738 (Critical), and will keep failing until the next release ships the apk upgrade fix.

Scanned with grype v0.118.0 and the workflow's flags, for linux/amd64.

🤖 Generated with Claude Code

A fresh build now runs apk upgrade, so it always has the latest Alpine
fixes and the scan passes even while the image on Docker Hub is still
vulnerable. Scan the published image, which is what users run, so a fix
waiting for a release gets noticed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@polius
polius merged commit ed13fe9 into main Nov 9, 2026
5 checks passed
@polius
polius deleted the ci/scan-published-image branch November 9, 2026 20:01
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