The generated promote rollback job (internal/generate/promote.go writeRollbackJobs) always emits uses: <deploy.Workflow>, with no inline-run branch (unlike writeDeployJobs, which supports a run: callback). A manifest that combines an inline run: deploy callback with rollback_on_failure therefore emits a rollback job referencing an empty workflow path, producing broken YAML at rollback time. Either emit an inline-run rollback branch mirroring the deploy job, or validate that rollback_on_failure requires reusable-workflow deploys. Found during e2e rollback-runtime scenario work (PR #118).
The generated promote rollback job (internal/generate/promote.go writeRollbackJobs) always emits
uses: <deploy.Workflow>, with no inline-run branch (unlike writeDeployJobs, which supports a run: callback). A manifest that combines an inline run: deploy callback with rollback_on_failure therefore emits a rollback job referencing an empty workflow path, producing broken YAML at rollback time. Either emit an inline-run rollback branch mirroring the deploy job, or validate that rollback_on_failure requires reusable-workflow deploys. Found during e2e rollback-runtime scenario work (PR #118).