Workflow support / Capability version 12
A growing subset.
Rookrunner v0.1.10 implements a versioned slice of workflow syntax and actions. Unsupported features fail planning; compatibility with hosted Actions is not implied.
Capability version 12The engine's reported capability version is 12. Check the release source and
describe output for the exact contract your integration consumes.Supported in this preview
- Local actions and local composite actions whose steps use
run. - Remote composite actions pinned to a full 40-character lowercase commit SHA.
- Remote Node 24 actions with
mainandpostentry points when a Node 24 runtime is supplied usingworker --node24. - Literal matrices, with up to 256 expanded jobs.
- Basic expression evaluation in conditions, run commands, environment, inputs, and names.
- Local reusable workflows and service containers with image, environment, command, and entrypoint settings.
- Artifact manifests and local storage for supported artifact workflows.
Known unsupported areas
hashFiles, matrix expressions, nesteduses, and remote reusable workflows.- Pre and Node 20 actions, Docker actions, and arbitrary action runtimes.
- Network port mapping for service containers.
- Job-level and composite-step
continue-on-error. Ordinary steps support a boolean or boolean expression. - Full GitHub context, expression, event, and action behavior.
The support surface changes by release. Read the v0.1.10 execution engine notes before depending on a boundary case. The planner reports unsupported capabilities instead of treating them as supported.
Runner image selection
The worker uses its --runner-image only when the submit omits --image and every selected job uses literal runs-on: ubuntu-latest. An explicit image takes precedence. Images must be digest-pinned for workflow execution; the operator supplies the image contents.