Skip to content

Commit 582c495

Browse files
authored
fix(ci): trigger publish workflow explicitly from release (#86)
## What Add explicit `gh workflow run publish.yml` step to release workflow, matching bashkit's approach. ## Why The `release.published` event doesn't chain when the GitHub Release is created by `GITHUB_TOKEN` — this is a known GitHub Actions limitation. The v0.2.0 publish required manual `workflow_dispatch`. ## How - Added `actions: write` permission to release workflow - Added step to explicitly trigger publish.yml after creating the release ## Risk - Low — CI-only change, matches proven bashkit pattern
1 parent e030b91 commit 582c495

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

.github/workflows/release.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ on:
88

99
permissions:
1010
contents: write
11+
actions: write
1112

1213
jobs:
1314
release:
@@ -64,3 +65,8 @@ jobs:
6465
body_path: release_notes.md
6566
draft: false
6667
prerelease: false
68+
69+
- name: Trigger publish workflow
70+
run: gh workflow run publish.yml
71+
env:
72+
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

0 commit comments

Comments
 (0)