neokapi/Setup Kapi CLI

Install the kapi CLI for CI workflows — downloads, verifies, caches, and configures the binary

Trust Signals

name	description	required	default
version	Kapi CLI version (e.g. '1.1.0' or 'latest' for the newest stable CLI release)	no	latest
token	GitHub token used for release downloads and API rate limits. The built-in GITHUB_TOKEN is sufficient now that neokapi/neokapi is public.	no	${{ github.token }}
plugins	Newline- or comma-separated plugin refs to install, as the registry names them (e.g. 'bowrain', 'okapi-bridge'). The 'kapi-' binary prefix is accepted and stripped ('kapi-bowrain' → 'bowrain'). Defaults to 'bowrain' so server-connected projects work out of the box; pass '' to install nothing.	no	bowrain
auth-token	Bowrain server JWT auth token (exported as BOWRAIN_AUTH_TOKEN)	no	""
server	Bowrain server URL (exported as BOWRAIN_SERVER_URL)	no	""
cache-tm	Restore and persist the project translation memory across CI runs via the job cache. The TM is derived state kept out of git (AD-009): the latest branch TM is restored at setup, and the grown TM is saved back at job end under a run-unique key, so leverage compounds without committing anything. A cold cache is fine — kapi rebuilds the TM from the committed translations. Runs only when a kapi.yaml recipe (or legacy *.kapi) is present. Set 'false' to disable.	no	true
project-dir	Directory holding the kapi.yaml project (recipe + state) for the TM cache. Default: repository root.	no	.

name	description
version	Installed kapi CLI version (e.g. '0.5.0')
cache-hit	Whether the plugin cache was hit