Commit f67e0fe
ci: trigger release after Dependabot Automerge
GitHub Actions doesn't fire `on: push` workflows when the push is
authenticated with GITHUB_TOKEN (intentional, to avoid recursive
workflow loops). pascalgn/automerge-action only has GITHUB_TOKEN, so
when it merges a Dependabot PR to default branch the resulting push
doesn't trigger Node.js Package and the version-bump + npm-publish job
never runs. Result: every Dependabot bump leaves an unreleased commit
on default branch, the published npm version drifts behind, and the
only way to ship is a human re-merge.
Two coupled changes:
- automerge.yml grows `actions: write` and a final step that calls
`gh workflow run test-and-release.yml --ref <default-branch>`.
Gated on automerge-action's `mergeResult == 'merged'` so it
doesn't fire when nothing actually merged.
- test-and-release.yml grows a `workflow_dispatch:` trigger so the
above invocation has something to dispatch. Existing on:push is
preserved unchanged.
Mirrors ep_announce#114 (already merged and verified end-to-end).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 9dcdb99 commit f67e0fe
2 files changed
Lines changed: 22 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2 | 2 | | |
3 | 3 | | |
4 | 4 | | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
5 | 11 | | |
6 | 12 | | |
7 | 13 | | |
| |||
21 | 27 | | |
22 | 28 | | |
23 | 29 | | |
| 30 | + | |
24 | 31 | | |
25 | 32 | | |
26 | 33 | | |
27 | 34 | | |
28 | 35 | | |
29 | 36 | | |
30 | 37 | | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | | - | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
3 | 9 | | |
4 | 10 | | |
5 | 11 | | |
| |||
0 commit comments