chore(auto-tag): explicitly dispatch release workflow after tag creation

Add a step to trigger the release notes workflow after creating a version tag. This ensures that the release notes are generated even when the tag push does not automatically trigger the workflow due to GitHub's recursion guard.

Impact: Users will receive timely release notes corresponding to new version tags.
This commit is contained in:
Julian Pawlowski 2026-07-04 18:34:31 +00:00
parent de6da790ab
commit 49ea70ed9f

View file

@ -9,6 +9,7 @@ on:
permissions: permissions:
contents: write contents: write
actions: write # Needed to explicitly dispatch release.yml (see note below)
concurrency: concurrency:
group: ${{ github.workflow }} group: ${{ github.workflow }}
@ -66,6 +67,22 @@ jobs:
echo "✅ Created and pushed tag: $TAG" echo "✅ Created and pushed tag: $TAG"
- name: Trigger release notes workflow
if: steps.tag_check.outputs.exists == 'false'
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
TAG="v${{ steps.manifest.outputs.version }}"
# NOTE: Tag pushes made with the default GITHUB_TOKEN do NOT trigger
# other workflows (GitHub's built-in recursion guard). Since we just
# pushed the tag above using GITHUB_TOKEN, release.yml's
# `push: tags: v*.*.*` trigger will NOT fire on its own.
# workflow_dispatch/repository_dispatch are exempt from that guard,
# so we explicitly dispatch release.yml here instead.
echo "::notice::Explicitly dispatching release.yml for $TAG (tag push via GITHUB_TOKEN does not auto-trigger workflows)"
gh workflow run release.yml --ref "$TAG" -f tag="$TAG"
- name: Summary - name: Summary
run: | run: |
if [ "${{ steps.tag_check.outputs.exists }}" = "true" ]; then if [ "${{ steps.tag_check.outputs.exists }}" = "true" ]; then