Tag uncached builds with the date
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>
This commit is contained in:
1 parent
0e1e97534f
commit
ae3636baab
2 files changed
+7
-1
No files matched your search
@@ -46,7 +46,7 @@ For x64 and arm64 (Raspberry Pi), add:
|
||||
| `context` | `.` | Docker build context. |
|
||||
| `file` | `<context>/Dockerfile` | Path to the Dockerfile. |
|
||||
| `build-args` | | Extra build args, one `NAME=value` per line, e.g. `APP_VERSION=${{ gitea.sha }}`. Used for both the scanned and the pushed build. |
|
||||
| `no-cache` | `false` | Build without cache. Use `${{ gitea.event_name == 'schedule' }}` so weekly rebuilds pick up new packages. |
|
||||
| `no-cache` | `false` | Build without cache. Use `${{ gitea.event_name == 'schedule' }}` so weekly rebuilds pick up new packages. Uncached builds are also tagged `YYYYMMDD` (UTC), which keeps each week's image as a rollback point. |
|
||||
| `severity` | `CRITICAL,HIGH` | Severities that fail the build. Vulnerabilities without a fixed version never fail it. |
|
||||
| `runs-on` | `linux-amd64` | Runner label. |
|
||||
|
||||
|
||||
Reference in new issue
Block a user