Erich Blume
1425bf1f5c
## Summary - consolidate forgejo-runner how-to docs into current cards - upgrade the k8s forgejo-runner deployment to the latest v12.8.x runner image - switch the k8s runner from first-boot register flow to declarative server.connections config - keep the runner image on the native Dagger build path and update the surrounding manifests/secrets ## Notes - PR opened early for C1 review - implementation and deployment verification will follow in subsequent commits Reviewed-on: #338
44 lines
1.1 KiB
Markdown
44 lines
1.1 KiB
Markdown
---
|
|
title: Validate Forgejo Workflows
|
|
modified: 2026-04-11
|
|
last-reviewed: 2026-04-20
|
|
tags:
|
|
- how-to
|
|
- forgejo-runner
|
|
- ci
|
|
---
|
|
|
|
# Validate Forgejo Workflows
|
|
|
|
Run `forgejo-runner validate` against all workflow files to catch schema issues before upgrading the k8s runner daemon.
|
|
|
|
## Result
|
|
|
|
All current workflows pass the validation step with no changes needed:
|
|
|
|
- `branch-cleanup.yaml` — OK
|
|
- `build-blumeops.yaml` — OK
|
|
- `build-container-nix.yaml` — OK
|
|
- `build-container.yaml` — OK
|
|
- `cv-deploy.yaml` — OK
|
|
- `deploy-fly.yaml` — OK
|
|
|
|
## Deliverables
|
|
|
|
1. `validate_workflows` function added to `src/blumeops/main.py` (formerly `.dagger/src/blumeops_ci/main.py`)
|
|
- Uses `forgejo-runner validate --directory .` inside the upstream runner container
|
|
- `runner_version` parameter pins validation to the deployed runner line
|
|
2. `mise run validate-workflows` task wired to `dagger call validate-workflows`
|
|
3. Pre-commit hook triggers on `.forgejo/workflows/` changes
|
|
|
|
## Usage
|
|
|
|
```fish
|
|
mise run validate-workflows
|
|
# or directly:
|
|
dagger call validate-workflows --src=.
|
|
```
|
|
|
|
## Related
|
|
|
|
- [[configure-k8s-runner]] — Runner configuration and upgrade flow
|