ci(release): pass explicit tag_name to softprops for dispatch runs - #110
Merged
Conversation
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).
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #109. The dispatched
v0.9.0-next.0release run published to npm but failed atCreate GitHub Release: dispatch runs carryGITHUB_REF_NAME=main, so softprops had no tag (⚠️ GitHub Releases requires a tag). Adds explicittag_namefrom the resolved release ref. npm publish is idempotent, so re-dispatch after merge only creates the missing GitHub Release.