From 36952ef48b4aa62d3ccaafa5c453bfd4f6d74236 Mon Sep 17 00:00:00 2001
From: Stephen Crowe <6042774+crowecawcaw@users.noreply.github.com>
Date: Tue, 14 Apr 2026 13:07:13 -0700
Subject: [PATCH] fix: use centralized build-python-version for PublishToPyPI

Use the build-python-version output from the shared TagRelease
workflow instead of a hardcoded Python version. This ensures all
repos stay in sync when build tool requirements change (e.g.
hatchling 1.29.0 requiring Python >=3.10).

Signed-off-by: Stephen Crowe <6042774+crowecawcaw@users.noreply.github.com>
---
 .github/workflows/release_publish.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/release_publish.yml b/.github/workflows/release_publish.yml
index ac8870010..d155af4a2 100644
--- a/.github/workflows/release_publish.yml
+++ b/.github/workflows/release_publish.yml
@@ -121,7 +121,7 @@ jobs:
       - name: Set up Python
         uses: actions/setup-python@v6
         with:
-          python-version: '3.13'
+          python-version: ${{ needs.TagRelease.outputs.build-python-version }}
       - name: Install dependencies
         run: |
           pip install --upgrade hatch