fix(publish): anchor gh release create to GITHUB_SHA to avoid untagged release

jdx · claude · jdx · commit 571ac7e3ecf0 · 2026-02-18T12:55:06.000Z
Without --target, gh release create resolves the tag via the GitHub API
which can race with tag propagation and create an untagged-* draft release
that taiki-e/upload-rust-binary-action cannot find by tag name.

Explicitly passing --target "$GITHUB_SHA" bypasses the tag lookup and
anchors the release to the exact commit SHA from the triggering event.

Co-Authored-By: Claude Sonnet 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/.github/workflows/publish-cli.yml b/.github/workflows/publish-cli.yml
@@ -33,7 +33,7 @@ jobs:
           TAG_NAME="${{ github.ref_name }}"
           # Extract first version section from CHANGELOG.md as baseline
           awk '/^## \[/{if(found) exit; found=1} found{print}' CHANGELOG.md >/tmp/release-notes.txt
-          gh release create --draft "$TAG_NAME" \
+          gh release create --draft --target "$GITHUB_SHA" "$TAG_NAME" \
             --title "$TAG_NAME" \
             --notes-file /tmp/release-notes.txt
       - name: Enhance release notes with communique
