fix(ci): lockstep-publish accepts workflow_dispatch — the repository-dispatch endpoint 404s on this forge #17
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/dispatch-trigger-fallback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The tool release workflows (dito/ditc R14 wiring) POST /repos/{owner}/{repo}/dispatches, which returns 404 on forge.deepnet.com (probed 2026-09-23; the workflow-dispatch endpoint works - 204). This workflow now also triggers on workflow_dispatch with {tool, version, channel} inputs, and the publish step reads inputs.X || github.event.client_payload.X so both trigger shapes feed the same step. The dispatchers switch to the workflow-dispatch endpoint in their own repos (dit-operator + dit-client companion PRs).
The tool release workflows (dito/ditc R14 wiring) POST to /repos/{owner}/{repo}/dispatches, which returns 404 on forge.deepnet.com (probed 2026-09-23; the workflow-dispatch endpoint works — 204). This workflow now also triggers on workflow_dispatch with {tool, version, channel} inputs, and the publish step reads inputs.X || github.event.client_payload.X so both trigger shapes feed the same step. The dispatchers switch to the workflow-dispatch endpoint in their own repos. Assisted-by: deepnet:synthetic/hf:zai-org/GLM-5.3-Flash