From c594274c838fcce42afaa8cf51d89045ab33c6ee Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Sat, 13 Jun 2026 00:41:20 +0000 Subject: [PATCH] ci: re-apply fire-planner stack after pipeline race MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Comment-only touch so the changed-stack detection applies stacks/fire-planner from the current master tree. Pipeline 150 (commit f18dfa4c — the ghcr image base + ghcr-credentials migration for issue #26) was auto-killed when the concurrent nextcloud-todos push superseded it, and pipeline 151 diffed from f18dfa4c onward so the fire-planner stack changes were never applied (cronjobs still point at the forgejo image, pod specs lack ghcr-credentials). Co-Authored-By: Claude Fable 5 --- stacks/fire-planner/main.tf | 3 +++ 1 file changed, 3 insertions(+) diff --git a/stacks/fire-planner/main.tf b/stacks/fire-planner/main.tf index 58321e69..817503e4 100644 --- a/stacks/fire-planner/main.tf +++ b/stacks/fire-planner/main.tf @@ -19,6 +19,9 @@ locals { # the ghcr-credentials Secret (kyverno sync-ghcr-credentials allowlist). # registry-credentials stays alongside so the currently-running sha-pinned # forgejo image remains pullable until the first ghcr deploy lands. + # (Applied via the 2026-06-13 re-trigger commit: the original pipeline 150 + # was auto-killed by a concurrent nextcloud-todos master push before its + # apply step ran, and the successor's diff base excluded this stack.) image = "ghcr.io/viktorbarzin/fire-planner:${var.image_tag}" labels = { app = "fire-planner"