Commit ce617a7
fix(release): use built-in GITHUB_TOKEN to dispatch recompile workflow (#923)
The post-release `trigger-recompile-safe-output-fixtures` job was using `secrets.GH_AW_CI_TRIGGER_TOKEN` to authenticate `gh workflow run`. That secret is a gh-aw runtime convention scoped to agentic workflows' safe-output PR creation; `release.yml` is a plain GitHub Actions workflow and shouldn't depend on it. When the secret is not provisioned (as on this repo today), the dispatch step fails with `GH_TOKEN` unset and the recompile never runs (see run 27193012425).
Switch the dispatch to the built-in `secrets.GITHUB_TOKEN` with an explicit `permissions: actions: write` scope. The dispatched recompile workflow continues to use its own secrets for any downstream PR creation, so no behavior is lost.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 9cf5f63 commit ce617a7
1 file changed
Lines changed: 9 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
191 | 191 | | |
192 | 192 | | |
193 | 193 | | |
194 | | - | |
195 | | - | |
196 | | - | |
197 | | - | |
198 | | - | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
199 | 200 | | |
200 | 201 | | |
201 | 202 | | |
202 | 203 | | |
203 | 204 | | |
| 205 | + | |
| 206 | + | |
204 | 207 | | |
205 | 208 | | |
206 | 209 | | |
207 | | - | |
| 210 | + | |
208 | 211 | | |
209 | 212 | | |
210 | 213 | | |
| |||
0 commit comments