From 802d2cef3fe36bccfbff264c5334a980b49c4e18 Mon Sep 17 00:00:00 2001
From: DevOps <devops@noveria.net>
Date: Tue, 9 Jun 2026 21:24:22 +0200
Subject: [PATCH] =?UTF-8?q?fix(ci):=20remove=20swagger=20from=20smoke=20te?=
 =?UTF-8?q?st=20=E2=80=94=20disabled=20in=20production?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Swagger (/swagger) is only enabled in Development mode (Program.cs
gates it behind app.Environment.IsDevelopment()). In production,
nginx serves the frontend catch-all (index.html), so the check
always returns 200 but never actually validates the API layer.

/health already covers API + database + runtime health checks.
No replacement endpoint needed — the smoke test still validates
both the dashboard and the backend API via /health.
---
 .gitea/workflows/deploy.yaml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/.gitea/workflows/deploy.yaml b/.gitea/workflows/deploy.yaml
index a48f825..f52c838 100644
--- a/.gitea/workflows/deploy.yaml
+++ b/.gitea/workflows/deploy.yaml
@@ -189,7 +189,7 @@ jobs:
       # ── Step 7: Smoke test (multi-endpoint) ───
       # Tests multiple endpoints to catch partial failures.
       # Why: a single /dashboard check can miss backend-only outages;
-      #   testing /api/swagger confirms the API layer is healthy too.
+      #   /health tests the API + database + runtime status.
       - name: Verify (smoke test)
         run: |
           echo "🔍 Smoke test..."
@@ -212,7 +212,6 @@ jobs:
 
           check "/dashboard" "Dashboard"    200
           check "/health"    "Health API"   200
-          check "/swagger"   "API Swagger"  200
 
           echo ""
           echo "Results: $PASS passed, $FAIL failed"