Upgrade k8s forgejo-runner from v6.3.1 to v12.7.0 #251

Merged
eblume merged 1 commit from upgrade-k8s-runner-v12 into main 2026-02-22 17:43:40 -08:00
Owner

Summary

Completes the upgrade-k8s-runner mikado chain. Both prerequisites (workflow validation in Dagger, config review against v12 defaults) were resolved in #250.

  • Bump runner image code.forgejo.org/forgejo/runner:6.3.112.7.0
  • Update service-versions.yaml to track new version
  • Mark goal card complete (remove status: active)

Deployment and Testing

After merge:

  1. argocd app sync forgejo-runner
  2. Verify runner registers in Forgejo admin → runners
  3. Trigger a test workflow (e.g. branch-cleanup.yaml manual dispatch)

Rollback: revert image tag to 6.3.1, push, sync.

## Summary Completes the `upgrade-k8s-runner` mikado chain. Both prerequisites (workflow validation in Dagger, config review against v12 defaults) were resolved in #250. - Bump runner image `code.forgejo.org/forgejo/runner:6.3.1` → `12.7.0` - Update `service-versions.yaml` to track new version - Mark goal card complete (remove `status: active`) ## Deployment and Testing After merge: 1. `argocd app sync forgejo-runner` 2. Verify runner registers in Forgejo admin → runners 3. Trigger a test workflow (e.g. `branch-cleanup.yaml` manual dispatch) Rollback: revert image tag to `6.3.1`, push, sync.
Completes the upgrade-k8s-runner mikado chain. Both prerequisites
(workflow validation and config review) were resolved in #250.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit e655f4556e into main 2026-02-22 17:43:40 -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!251
No description provided.