Commit 379dbc2
committed
Fix release workflow: add explicit tag_name for GitHub Release
The softprops/action-gh-release action requires an explicit tag_name
when triggered via workflow_run, because github.ref in that context
points to refs/heads/master (a branch), not the tag.
Without tag_name, the action fails with: "GitHub Releases requires a tag"
This fix adds tag_name using the version from the identifiers workflow,
which correctly detected the tag via git describe --tags --exact-match.
Note: This work was completed with AI assistance (Claude Code).1 parent 010bf8d commit 379dbc2
1 file changed
Lines changed: 16 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
282 | 282 | | |
283 | 283 | | |
284 | 284 | | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
| 288 | + | |
| 289 | + | |
| 290 | + | |
| 291 | + | |
| 292 | + | |
| 293 | + | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
| 297 | + | |
| 298 | + | |
| 299 | + | |
285 | 300 | | |
286 | 301 | | |
287 | 302 | | |
| 303 | + | |
288 | 304 | | |
289 | 305 | | |
290 | 306 | | |
| |||
0 commit comments