Skip to content

Commit d93ac75

Browse files
ci(release): pass explicit tag_name to softprops for dispatch runs (#110)
* ci(release): add workflow_dispatch fallback for tag-push event gaps Push/tag events have intermittently failed to enqueue runs (merges to main after 2026-08-26T14:55Z created no CI runs), blocking tag-triggered publishes. Adds a manual trigger with a required tag input; the job resolves RELEASE_REF_NAME once, checks out the tag's exact commit, and all tag-derived steps use it instead of GITHUB_REF_NAME (mirrors ci.yml's dispatch-scoped model-data-drift pattern). * ci(release): pass explicit tag_name to softprops for dispatch runs The first workflow_dispatch release run published to npm but failed at 'Create GitHub Release' — with GITHUB_REF_NAME=main, softprops had no tag to attach the release to.
1 parent e8c61c8 commit d93ac75

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

.github/workflows/release.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,9 @@ jobs:
128128
- name: Create GitHub Release
129129
uses: softprops/action-gh-release@v3
130130
with:
131+
# Dispatch runs carry the branch ref; GITHUB_REF_NAME isn't the tag
132+
# there, so pass the resolved tag explicitly.
133+
tag_name: ${{ steps.ref.outputs.RELEASE_REF_NAME }}
131134
name: "v${{ steps.version.outputs.VERSION }}"
132135
generate_release_notes: true
133136
prerelease: ${{ steps.version.outputs.PRERELEASE }}

0 commit comments

Comments
 (0)