eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/how-to/forgejo-runner/validate-workflows-against-v12.md
Erich Blume 215ebef73e Update docs for Dagger module restructure 
- Update dagger.md reference card: new module name, source path,
  container build types table, container-version function
- Update build-container-image.md: container.py as preferred for indri,
  default.nix for ringtail, navidrome as reference pattern
- Update upgrade-dagger.md: uv.lock path (no longer under .dagger/)
- Update .dagger/src/blumeops_ci path references across 5 how-to docs
- Update container-version-check and pin-container-versions docs
- Update mise-tasks reference
- Set modified: 2026-04-11 on all changed docs

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-11 17:09:51 -07:00

1.2 KiB
Raw Blame History

title modified last-reviewed tags
Validate Workflows Against v12 2026-04-11 2026-02-27
how-to
forgejo-runner
ci

Validate Workflows Against v12

Run forgejo-runner validate (available from v9.0+) against all workflow files to catch schema issues before upgrading the k8s runner daemon.

Result

All 6 workflows pass v12.7.0 schema validation 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 (default 12.7.0) pins to deployed version
  2. mise run validate-workflows task wired to dagger call validate-workflows
  3. Pre-commit hook triggers on .forgejo/workflows/ changes

Usage

mise run validate-workflows
# or directly:
dagger call validate-workflows --src=.

Related