Skip to content

fix(ci): no-cache + pull on container scan #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
amavashev merged 1 commit into from
May 3, 2026
Merged

fix(ci): no-cache + pull on container scan #164

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions .github/workflows/pr-container-scan.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,8 +53,13 @@ jobs:
tags: ghcr.io/runcycles/cycles-server-admin:scan-${{ github.event.pull_request.number || github.sha }}
build-args: |
APP_VERSION=scan-${{ github.event.pull_request.number || github.sha }}
cache-from: type=gha
cache-to: type=gha,mode=max
# no-cache + pull are critical for security scans: cached layers
# (especially `apk upgrade`) keep reporting old packages even
# after a base-image bump. Witnessed in cycles-dashboard PR #157
# / #158 — FROM bump didn't take effect because cached layer
# served months-old apk state. Always build fresh for scans.
no-cache: true
pull: true

- name: Trivy vulnerability scan
uses: aquasecurity/trivy-action@ed142fd0673e97e23eac54620cfb913e5ce36c25 # v0.36.0
Expand Down
Loading