From 3e08720b439c677b4b53a4fedb370a0db07cf2ca Mon Sep 17 00:00:00 2001
From: Ryan Walters <ryan@walters.to>
Date: Sat, 22 Nov 2025 21:43:04 -0600
Subject: [PATCH] fix(ci): correct Railway CLI invocation in GitHub Actions

The deployment was failing because the workflow used incorrect syntax
with `uses: docker://` which caused Docker to misinterpret `up` as an
executable rather than an argument to the Railway CLI.

Split deployment into a separate job using `container:` at the job level,
allowing the Railway CLI to execute properly. This follows Railway's
official documentation for GitHub Actions integration.
---
 .github/workflows/deploy.yaml | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/.github/workflows/deploy.yaml b/.github/workflows/deploy.yaml
index 136ffed..accf3cf 100644
--- a/.github/workflows/deploy.yaml
+++ b/.github/workflows/deploy.yaml
@@ -120,10 +120,14 @@ jobs:
       - name: Wait for registry propagation
         run: sleep 5
 
-      # Deploy to Railway
+  # Deploy to Railway - separate job to use container properly
+  deploy:
+    name: Deploy to Railway
+    runs-on: ubuntu-latest
+    needs: build-and-deploy
+    container: ghcr.io/railwayapp/cli:latest
+    env:
+      RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
+    steps:
       - name: Deploy to Railway
-        uses: docker://ghcr.io/railwayapp/cli:latest
-        env:
-          RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
-        with:
-          args: up --service pac-man
+        run: railway up --service pac-man