ci: call homebrew-bump as reusable workflow instead of PAT event propagation #53

Merged
razvandimescu merged 1 commits from ci/release-workflow-call-homebrew-bump into main 2026-04-10 04:33:48 +08:00
2 changed files with 16 additions and 16 deletions

View File

@@ -1,8 +1,12 @@
name: Bump Homebrew Tap name: Bump Homebrew Tap
on: on:
release: workflow_call:
types: [published] inputs:
version:
description: 'Version to bump (e.g. 0.10.0 or v0.10.0)'
type: string
required: true
workflow_dispatch: workflow_dispatch:
inputs: inputs:
version: version:
@@ -20,13 +24,10 @@ jobs:
- name: Determine version - name: Determine version
id: ver id: ver
env:
INPUT_VERSION: ${{ inputs.version }}
run: | run: |
if [ "${{ github.event_name }}" = "release" ]; then V="${INPUT_VERSION#v}"
V="${{ github.event.release.tag_name }}"
else
V="${{ github.event.inputs.version }}"
fi
V="${V#v}"
echo "version=$V" >> "$GITHUB_OUTPUT" echo "version=$V" >> "$GITHUB_OUTPUT"
- name: Fetch sha256 checksums from release assets - name: Fetch sha256 checksums from release assets

View File

@@ -103,16 +103,15 @@ jobs:
- name: Create Release - name: Create Release
uses: softprops/action-gh-release@v2 uses: softprops/action-gh-release@v2
with: with:
# Use a PAT (not the default GITHUB_TOKEN) so the resulting
# `release: published` event propagates to downstream workflows
# like homebrew-bump.yml. Events triggered by GITHUB_TOKEN are
# deliberately not propagated by GitHub Actions to prevent
# infinite loops; PAT-authored events are the documented escape
# hatch. Reusing HOMEBREW_TAP_GITHUB_TOKEN (already a PAT used
# by homebrew-bump.yml itself) keeps the secret surface flat.
token: ${{ secrets.HOMEBREW_TAP_GITHUB_TOKEN }}
generate_release_notes: true generate_release_notes: true
files: | files: |
*.tar.gz *.tar.gz
*.zip *.zip
*.sha256 *.sha256
bump-homebrew:
needs: release
uses: ./.github/workflows/homebrew-bump.yml
with:
version: ${{ github.ref_name }}
secrets: inherit