From 5e7c7540127724fecac8f5e3e2223ae0b99cadbe Mon Sep 17 00:00:00 2001 From: Guido X Jansen Date: Sat, 28 Feb 2026 12:21:50 +0100 Subject: [PATCH] fix(deploy): use real Bluesky handle in login verification check test.bsky.social doesn't resolve to a DID, so the login endpoint returns 502. Use bsky.app which is a known-valid handle. --- .github/workflows/deploy-staging.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy-staging.yml b/.github/workflows/deploy-staging.yml index 4568a4b..a5304f3 100644 --- a/.github/workflows/deploy-staging.yml +++ b/.github/workflows/deploy-staging.yml @@ -324,9 +324,10 @@ jobs: # Retry up to 6 times (30s total) -- API may still be starting after deploy # Use 127.0.0.1 (not localhost) -- Alpine may not resolve localhost to IPv4 + # Use a real Bluesky handle -- the API resolves the DID via the AT Protocol for i in $(seq 1 6); do RESPONSE=$(docker compose ${{ env.COMPOSE_FILES }} exec -T barazo-api \ - wget -qO- "http://127.0.0.1:3000/api/auth/login?handle=test.bsky.social" 2>&1 || true) + wget -qO- "http://127.0.0.1:3000/api/auth/login?handle=bsky.app" 2>&1 || true) if echo "$RESPONSE" | grep -q '"url"'; then echo "Login endpoint OK: response contains redirect URL (attempt $i/6)" -- 2.51.2