ci(publish): add a manual build-only rehearsal trigger
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / Lint + typecheck (pull_request) Successful in 1m10s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Successful in 9s
PR Check / Dockerfile lint (droast) (pull_request) Successful in 5s

workflow_dispatch with version/push/latest inputs: push defaults to
false, so the runner, socket and registry login can be verified without
creating a tag or a package version. latest is never moved unless asked.
This commit is contained in:
Noel Sabia committed 2026-10-31 21:08:39 +01:00
1 parent 7981575f86
commit 3614bfd3ae
3 files changed
+75 -4

No files matched your search

+19
View File
@@ -142,6 +142,25 @@ appears in the process list or the log.
4. Namespace `cv` has an `imagePullSecret` for the same credentials.
5. `git.noelsabia.dev` answers over HTTPS.
# Manual rehearsal (workflow_dispatch)
The workflow can be started from the Gitea UI (Actions → Publish image →
Run workflow) without creating a tag:
| Input | Use |
|---|---|
| `version` | required, `vMAJOR.MINOR.PATCH` |
| `push` | `false` (default) builds and smoke-tests only; `true` publishes |
| `latest` | `false` unless this is a real release |
A build-only run publishes nothing, so it creates no package version and
the immutability guard is skipped. This is the way to prove the runner,
socket and registry login before the first release - a rehearsal must never
move `latest`, which is why that input is explicit.
Gitea only offers the Run-workflow button for workflows present on the
default branch, so this trigger is available once the change is on `main`.
# Guards in the workflow
| Guard | Why |