Commit 5cc18c2
## Description
Fix the auto-publish chain where `publish.yml` was not triggered after
`auto-release.yml` created a GitHub release. This is because GitHub
Actions events created by `GITHUB_TOKEN` don't trigger other workflows,
but `workflow_dispatch` is an exception to this limitation.
## Type of Change
- [x] Bug fix
## Changes Made
- Added `workflow_dispatch:` trigger to `publish.yml` so it can be
invoked via `gh workflow run`
- Added a "Trigger publish workflow" step in `auto-release.yml` that
runs `gh workflow run publish.yml` after creating a release, using the
same condition (`steps.check_tag.outputs.exists == 'false'`)
## Related Issues
Closes #21
## Testing
- [x] Manual review of workflow YAML syntax
- [x] Verified the `workflow_dispatch` trigger is a known exception to
the GITHUB_TOKEN limitation
## Checklist
- [x] My code follows the project's code style
- [x] I have performed a self-review of my code
- [x] My changes generate no new warnings
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 39792b8 commit 5cc18c2
2 files changed
Lines changed: 8 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
34 | 34 | | |
35 | 35 | | |
36 | 36 | | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| 6 | + | |
6 | 7 | | |
7 | 8 | | |
8 | 9 | | |
| |||
0 commit comments