JavaScript actions
node20 · node24
Main, pre, and post entrypoints run with action inputs, outputs, state, environment files, and lifecycle ordering preserved.
GitHub Actions compatibility
Actions are supported by runtime, not by allowlist.
Runnable supports Marketplace actions, actions from reachable repositories, and local actions that fit its Linux x64 execution contract. An action publisher does not need to build a Runnable integration: JavaScript, composite, and Docker actions are resolved at the referenced version and executed directly by Runnable.
No curated Marketplace allowlist
The action formats Runnable executes
Compatibility follows the action's metadata and dependencies, regardless of who published it.
Composite actions
local · repository · nested
Nested actions are resolved recursively, with conditions, environment changes, outputs, and cleanup carried through the composite.
Docker actions
Dockerfile · docker://
Runnable builds or pulls the image and preserves the workspace mount, container paths, environment, entrypoint, arguments, and action state.
Native service integrations
A few official actions need more than a runtime.
Checkout establishes the job workspace; cache and artifact actions normally talk to GitHub Actions-owned storage services. Runnable handles these actions natively so the job remains independent of the GitHub Actions control plane. Their exact version and input contracts are documented below.
actions/checkout
Checkout
Native parity for v4 – v6
15 supported inputs· 5 not implemented
actions/cache
Cache
Native parity for v3 – v5
8 supported inputs
actions/upload-artifact
Upload artifact
Native parity for v4
7 supported inputs
actions/download-artifact
Download artifact
Native parity for v4
8 supported inputs
Explicit boundaries
Broad support without vague promises.
The boundary is the machine, runtime, hosted services, and security contract—not whether an action appears in a list.
Runner platform
Runnable is Linux x64. Actions that require Windows, macOS, ARM, GPUs, or another runner image are outside the current contract.
Action runtime
JavaScript actions must use Node 20 or Node 24. Composite run steps must use bash, sh, or a bash/sh command template.
Hosted services
An action that calls an unimplemented GitHub Actions cache, artifact, runtime, or results service is reported runtime-dependent instead of being allowed to fail halfway through a job.
Credentials and network
Actions can reach public internet endpoints, while private and metadata networks remain blocked. Write-scoped GitHub tokens require both an explicit workflow permission and the matching GitHub App grant.
How the checker reaches a verdict
Full
The exact action ref, runtime, entrypoints, and nested dependencies were resolved and fit the Runnable contract.
Runtime-dependent
The workflow alone cannot prove the action, or the action depends on a hosted service that Runnable does not provide.
Unsupported
The action crosses an explicit runtime, platform, input, or security boundary and is rejected before dispatch.
Check the actions you actually use
Runnable resolves the whole workflow and reports each action against the current contract. No account is required, and workflow source is never retained.