Commit df30125
committed
fix(ci): docker-publish version tag missing on workflow_dispatch
When docker-publish.yml is dispatched via workflow_dispatch (the
backfill path for tags that were created with GITHUB_TOKEN and didn't
fire downstream workflows), `type=ref,event=tag` produced no version
tag — that pattern only fires on push:tag events. Result: the v0.9.0
GHCR image was pushed but only got the `:latest` tag, not `:v0.9.0`.
Diagnosis: GHCR anonymous tags-list API after the v0.9.0 dispatch
shows only `latest`:
curl -fsS -H "Authorization: Bearer $token" \
https://ghcr.io/v2/dfrostar/neuralmind/tags/list
→ {"name":"dfrostar/neuralmind","tags":["latest"]}
Fix: switch to `type=raw,value=${{ env.RELEASE_TAG }}` which works
for both event paths (push:tag → RELEASE_TAG=github.ref_name,
workflow_dispatch → RELEASE_TAG=inputs.tag). The verify-pull job
already reads the first tag from metadata-action outputs, so it
naturally pulls the version-specific tag for its smoke test.
After this merges, the v0.9.0 image needs to be re-built:
gh workflow run docker-publish.yml --ref main -f tag=v0.9.0
This will overwrite `:latest` (same content) and create `:v0.9.0`.
Future push:tag runs (once RELEASE_PLEASE_TOKEN is set per #98) are
also fixed by the same change — RELEASE_TAG is set from
github.ref_name in env, and type=raw reads it directly.
https://claude.ai/code/session_01SH6iHNAqeMJHXdq7ubVcuJ1 parent 4c8550e commit df30125
1 file changed
Lines changed: 8 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
69 | 69 | | |
70 | 70 | | |
71 | 71 | | |
72 | | - | |
73 | | - | |
74 | | - | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
75 | 79 | | |
76 | | - | |
| 80 | + | |
77 | 81 | | |
78 | 82 | | |
79 | 83 | | |
| |||
0 commit comments