Repository navigation
Commit a7c846d
Trigger push_gem workflow after tagging, and allow manual dispatch
Publishing 4.14.0 tagged v4.14.0 and created the GitHub release, but
push_gem.yml did not run and no gem was pushed to RubyGems.
Root cause: GitHub Actions does not trigger downstream workflows for
events driven by GITHUB_TOKEN. script/publish now runs inside the
publish-release workflow, which uses GITHUB_TOKEN for its checkout —
so the 'git push origin v4.14.0' from that job does not fire the
'push: tags: v*' event on push_gem.yml. Previous releases were tagged
by a maintainer running script/publish locally with a PAT, which is
why push_gem always fired for them.
Two changes:
- Add a workflow_dispatch trigger to push_gem.yml with a required
'tag' input, and check that tag out. This lets a maintainer manually
push the gem for a specific tag (needed right now to publish v4.14.0
to RubyGems).
- At the end of script/publish, dispatch push_gem.yml with the freshly
created tag. || true so any dispatch failure never masks a successful
release. This makes future releases push the gem automatically even
when script/publish runs from Actions.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 217f0a0d-a9f2-4607-9643-5fcb3e34f20f1 parent b7094df commit a7c846d
2 files changed
Lines changed: 17 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
7 | 13 | | |
8 | 14 | | |
9 | 15 | | |
| |||
29 | 35 | | |
30 | 36 | | |
31 | 37 | | |
| 38 | + | |
32 | 39 | | |
33 | 40 | | |
34 | 41 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
71 | 71 | | |
72 | 72 | | |
73 | 73 | | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
0 commit comments