From 9a61cad54bc1b4fb68a3e1c08f4202c535add7c9 Mon Sep 17 00:00:00 2001
From: Marco Wende <marco.wende@wende.it>
Date: Fri, 21 Aug 2026 00:37:54 +0200
Subject: [PATCH] CI: Gitea-Upload-Schritt loggt Token-Laenge zur Diagnose

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .github/workflows/release.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 6d59f24..1dbd0ab 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -119,8 +119,10 @@ jobs:
           MSI_NAME:    ${{ steps.build.outputs.MSI_NAME }}
           COMMIT_SHA:  ${{ github.sha }}
         run: |
+          $tokLen = if ([string]::IsNullOrEmpty($env:GITEA_TOKEN)) { 0 } else { $env:GITEA_TOKEN.Length }
+          Write-Host "Diagnose: GITEA_TOKEN Laenge = $tokLen (0 = Secret erreicht den Lauf nicht)"
           if ([string]::IsNullOrWhiteSpace($env:GITEA_TOKEN)) {
-            Write-Host "::notice::GITEA_TOKEN nicht gesetzt — Gitea-Upload uebersprungen."
+            Write-Host "::warning::GITEA_TOKEN leer (Laenge=$tokLen) — Gitea-Upload uebersprungen. Muss ein REPOSITORY-Secret sein unter Settings > Secrets and variables > Actions (Tab 'Secrets', NICHT 'Variables'), Name exakt GITEA_TOKEN, im Repo mwende/Intune-Manager."
             exit 0
           }
           $headers = @{ Authorization = "token $env:GITEA_TOKEN" }