The weekly rebuild overwrites latest/main/<sha> with a fresh image of
the same commit; a YYYYMMDD tag keeps each week's image to roll back to.
Keyed on no-cache, since a called workflow never sees the schedule event.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Extra NAME=value build args, passed to both the scanned and the pushed
build, for repos that bake more than VERSION into the image.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The run page is addressed by run ID, not run number, and event_name is
always workflow_call in a called workflow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Optional: runs only if variable NTFY_URL is set. Trivy failures list the
CVE IDs, other failures name the branch; both link to the run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- no-cache input for scheduled rebuilds that must pick up new packages
- The push step no longer reads the registry cache, only the layers the
scan step just built, so the pushed image is the scanned one even on
no-cache runs
- Put --build-arg back on its own line
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Pass the image version as build arg VERSION to both the scan and push
builds, so the scanned image matches the pushed one
- Limit BuildKit to 8 parallel steps (as mqtt-influx-bridge did)
- Update actions to checkout@v7, setup-qemu@v4, setup-buildx@v4,
login@v4, metadata@v6, build-push@v7
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>