README: repos follow main, no v1 tag

The usage example now includes the weekly uncached rebuild.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
thomas.gloorandClaude Opus 5.5 committed 2026-10-26 10:39:52 +01:00
1 parent 12e4594cfe
commit 0e1e97534f
1 file changed
+13 -8
+13 -8
View File
@@ -17,13 +17,20 @@ on:
push:
branches: [main]
tags: ['v*', '[0-9]*']
schedule:
- cron: '0 19 * * 5' # Fri 20:00 CET / 21:00 CEST (cron is UTC)
workflow_dispatch:
jobs:
build:
uses: ci/workflows/.gitea/workflows/docker-build.yml@v1
uses: ci/workflows/.gitea/workflows/docker-build.yml@main
with:
# Weekly rebuilds skip the cache so base image and package updates get in.
no-cache: ${{ gitea.event_name == 'schedule' }}
secrets: inherit
```
The weekly rebuild catches new CVEs in images whose code hasn't changed.
For x64 and arm64 (Raspberry Pi), add:
```yaml
@@ -74,14 +81,12 @@ repo root, with a reason:
CVE-2026-12345
```
### Tags
### Changing this workflow
Repos reference `@v1`. Test changes on one repo by pointing it at a branch or
commit, then move the `v1` tag:
```sh
git tag -f v1 && git push -f origin v1
```
Repos reference `@main`, so a push here reaches all of them on their next
build. Check a change with one run (e.g. a manual run of a small repo) before
moving on, and avoid pushing untested changes before the Friday rebuild. To
undo, revert the commit; every repo picks up the revert the same way.
Upgrading Trivy: change `TRIVY_IMAGE` in `docker-build.yml` and the image of
the `Gitea-Trivy` container to the same version.