From 54555b210180d0ad24ddaf6dab6b749ff82ae38a Mon Sep 17 00:00:00 2001
From: Alireza Eliaderani <172368+cubny@users.noreply.github.com>
Date: Fri, 10 Jul 2026 17:03:30 +0200
Subject: [PATCH] Add Fly.io deploy workflow triggered on release

Releases previously ran goreleaser only, which publishes binaries to the
GitHub Release. Nothing built or pushed an image to fly.io, so every
deploy since the app launched was a manual `fly deploy`. Tagging v3.3.1
therefore left production running the May 20 image.

Deploy on `release: created` to match the existing release.yml trigger,
plus workflow_dispatch for manual re-runs. Authenticates with a
deploy-scoped FLY_API_TOKEN stored in repo secrets.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .github/workflows/fly-deploy.yml | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 .github/workflows/fly-deploy.yml

diff --git a/.github/workflows/fly-deploy.yml b/.github/workflows/fly-deploy.yml
new file mode 100644
index 0000000..9e3c558
--- /dev/null
+++ b/.github/workflows/fly-deploy.yml
@@ -0,0 +1,24 @@
+name: Deploy to Fly.io
+on:
+  release:
+    types: [created]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+# Never let two deploys race; a newer release supersedes an in-flight one.
+concurrency:
+  group: fly-deploy
+  cancel-in-progress: false
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: superfly/flyctl-actions/setup-flyctl@master
+      - name: Deploy
+        run: flyctl deploy --remote-only
+        env:
+          FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}