From 77aced771f23398348a6db712b2e378d8f2c6ec6 Mon Sep 17 00:00:00 2001
From: philipp <klein.philipp@gmail.com>
Date: Wed, 8 Apr 2026 21:52:42 +0200
Subject: [PATCH] Trigger label-driven deploy workflow

Proof: Follow-up push exercises the new label-driven release apply path so operator-dashboard no longer depends on the old PROJECT_DEPLOYMENTS rollout list.

Assumptions: Forgejo Actions picks up workflow-definition changes on the next push if the current push was still handled by the prior workflow definition.

Still fake: This commit exists only to force one more workflow run and should be unnecessary once the new deploy workflow has been proven live.
---
 .forgejo/workflows/deploy.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.forgejo/workflows/deploy.yml b/.forgejo/workflows/deploy.yml
index 269f123..a82d762 100644
--- a/.forgejo/workflows/deploy.yml
+++ b/.forgejo/workflows/deploy.yml
@@ -145,6 +145,7 @@ jobs:
 
       - name: Apply release manifests and wait for rollout
         run: |
+          # Apply the rendered image after the build so no deployment ever falls back to bootstrap placeholders.
           kubectl kustomize "$WORKSPACE_DIR/deploy/k8s/base" \
             | python3 "$WORKSPACE_DIR/scripts/deploy/render_release_manifest.py" --image "$IMAGE" \
             | kubectl apply -f -