Upgrade k8s forgejo-runner from v6.3.1 to v12.x #249

Merged
eblume merged 1 commit from upgrade-forgejo-runner into main 2026-02-22 17:12:46 -08:00
Owner

Summary

  • C2 Mikado chain for upgrading the k8s forgejo-runner daemon (6 major versions behind)
  • Root goal card with two leaf prerequisites: workflow validation and config review
  • Ringtail runner is already at ~v12.6.4 via nixpkgs, no work needed there

Mikado Chain

upgrade-k8s-runner (goal)
├── validate-workflows-against-v12 (leaf)
└── review-runner-config-v12 (leaf)

Both leaves are actionable now. The biggest risk is workflow schema validation
(introduced in v8/v9) rejecting our existing workflows.

Next Steps

Work the leaf nodes in a follow-up session, then attempt the goal.

🤖 Generated with Claude Code

## Summary - C2 Mikado chain for upgrading the k8s forgejo-runner daemon (6 major versions behind) - Root goal card with two leaf prerequisites: workflow validation and config review - Ringtail runner is already at ~v12.6.4 via nixpkgs, no work needed there ## Mikado Chain ``` upgrade-k8s-runner (goal) ├── validate-workflows-against-v12 (leaf) └── review-runner-config-v12 (leaf) ``` Both leaves are actionable now. The biggest risk is workflow schema validation (introduced in v8/v9) rejecting our existing workflows. ## Next Steps Work the leaf nodes in a follow-up session, then attempt the goal. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
C2 change: three cards documenting the upgrade path, breaking changes,
and prerequisites (workflow validation, config review).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume force-pushed upgrade-forgejo-runner from 671de346f1 to a907a6cd5e 2026-02-22 17:01:39 -08:00 Compare
eblume force-pushed upgrade-forgejo-runner from a907a6cd5e to 1a9c8c4386 2026-02-22 17:11:14 -08:00 Compare
eblume force-pushed upgrade-forgejo-runner from 1a9c8c4386 to dac670a594 2026-02-22 17:12:33 -08:00 Compare
eblume merged commit 00b0287bcc into main 2026-02-22 17:12:46 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!249
No description provided.