From 0c48ddc6da8da6f83146c1483ade92866eca96b5 Mon Sep 17 00:00:00 2001
From: Brandon Harvey <8107750+bharvey88@users.noreply.github.com>
Date: Fri, 24 Jul 2026 10:59:04 -0500
Subject: [PATCH] Re-point beta-fw tag on every beta publish
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The rolling beta-fw release tag was stuck on the commit that was
default-branch HEAD when the release was first created. gh release
create without --target tags default-branch HEAD, and gh release
upload never moves the tag, so the published assets tracked every
beta build while the release source commit did not.

Adds a step to build-beta.yml that PATCHes the beta-fw tag ref to
the built commit after each upload, so the tag always matches the
assets.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
---
 .github/workflows/build-beta.yml | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/.github/workflows/build-beta.yml b/.github/workflows/build-beta.yml
index 1a990cd..29b0347 100644
--- a/.github/workflows/build-beta.yml
+++ b/.github/workflows/build-beta.yml
@@ -103,3 +103,14 @@ jobs:
               gh release upload beta-fw {} -R "${{ github.repository }}" --clobber \;
           done
           echo "Beta assets published."
+
+      - name: Point beta-fw tag at the built commit
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          # gh release create tags default-branch HEAD, and uploads never move
+          # the tag, so without this the release's source commit drifts away
+          # from the assets actually published.
+          gh api -X PATCH "repos/${{ github.repository }}/git/refs/tags/beta-fw" \
+            -f sha="${{ github.sha }}" -F force=true
+          echo "beta-fw -> ${{ github.sha }}"