ci: take the reusable that reads the lock instead of hunting a tag

v1.0.49's client lane decided check-vs-move from `github.event_name`, which
git.hanzo.ai renders as `workflow_call` inside every reusable, so this repo's
pushes ran as MOVEs and went looking for hanzoai/cloud's newest tag. That tag
is v1.801.507, which is not on cloud's main and carries no openapi.yaml, so the
fetch 404'd and took the job with it.

v1.0.54 asks the payload instead: with none, the ref is the one .spec-lock
already names, which is what a check is and what a push wants.
This commit is contained in:
zooqueen
2026-08-12 21:11:18 -07:00
parent 1fe73de0c3
commit 04a818ba12
+1 -1
View File
@@ -38,5 +38,5 @@ on:
workflow_dispatch:
jobs:
cicd:
uses: hanzoai/ci/.hanzo/workflows/[email protected]9
uses: hanzoai/ci/.hanzo/workflows/[email protected].54
secrets: inherit