From a9dc4e7b437ed7baad83dbb4ba5877aec816cb02 Mon Sep 17 00:00:00 2001 From: Jac Fitzgerald Date: Wed, 8 Jul 2026 12:48:41 -0700 Subject: [PATCH] fix: explicitly dispatch package.yml after tag push GITHUB_TOKEN-based tag pushes do not trigger other workflows, so package.yml never fired automatically. Dispatch it explicitly after creating the draft release. Co-Authored-By: Claude Sonnet 4.6 --- .github/workflows/release-on-merge.yml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release-on-merge.yml b/.github/workflows/release-on-merge.yml index 28c3dff1..cb324af0 100644 --- a/.github/workflows/release-on-merge.yml +++ b/.github/workflows/release-on-merge.yml @@ -1,8 +1,9 @@ name: Draft release on merge to main # Triggers when a PR is merged into main (push to main covers all merge strategies). -# Creates a draft GitHub release with auto-generated notes and pushes the version tag. -# The tag push triggers package.yml to build and attach binaries. +# Creates a draft GitHub release with auto-generated notes, pushes the version tag, +# and explicitly dispatches package.yml to build and attach binaries. +# (Tag pushes from GITHUB_TOKEN do not trigger other workflows, so we dispatch explicitly.) # When you publish the draft release, publish-pypi.yml uploads to PyPI automatically. on: @@ -58,3 +59,9 @@ jobs: --title "$TAG" \ --generate-notes \ --notes-start-tag "$LAST_TAG" + + - name: Trigger binary builds + env: + GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} + TAG: ${{ steps.version.outputs.tag }} + run: gh workflow run package.yml --ref "$TAG"