From 978e7419ffcf5ad5cef285e16333fdd45a66d047 Mon Sep 17 00:00:00 2001
From: Tane Morgan <464864+tanem@users.noreply.github.com>
Date: Sat, 8 Aug 2026 16:49:39 +1200
Subject: [PATCH] Read the default branch in the release guard
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The guard named `master` outright. That is correct here and will stay
correct, so this is not a fix — it is alignment with the shape the fleet
documents, now that tanem/release-action's README and the decision spec
both read the default branch rather than naming one.

The reading form exists because a literal is a trap in anything copied:
name a branch the repo does not have and every release skips, silently
and forever. tanem/release-action itself is on main, and GitHub creates
new repos on main, while every existing fleet repo is on master.

Keeping all the fleet's release workflows on one form means a future
reader diffing them against the spec finds no drift to explain.
---
 .github/workflows/release.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index b0c0c02d6..a6f199bba 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -23,7 +23,7 @@ jobs:
     # The cron only ever fires on the default branch, but a manual dispatch can
     # target any branch. Without this guard, dispatching against a version
     # branch would bump, tag and publish that branch to npm as latest.
-    if: github.ref == 'refs/heads/master'
+    if: github.ref_name == github.event.repository.default_branch
 
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1