Repository navigation
Raft v0.7.0
Raft 0.7.0
- Disposable foreground CI jobs.
raft run -- COMMAND ...creates a fresh disposable box, waits for readiness, streams one command and attempts ownership-checked cleanup after success, failure or cancellation. Use the existing location, size, snapshot-template and note options. This is remote job orchestration, not a registered GitHub runner or paid Boat integration. - Source and result transfers.
--push DIRECTORYuploads Git-tracked and unignored files without Git metadata; submodules are rejected.--push-all DIRECTORYexplicitly includes hidden and ignored files. Repeated--pull GUEST_DIRECTORY NEW_LOCAL_DIRECTORYoptions collect results before cleanup, including after a failed command.--cwdselects the guest working directory. - Bounded lifetimes and cancellation-safe cleanup. A single timeout covers preparation through command execution, followed by bounded collection and cleanup grace periods. A unique run identity and fixed expiry are set before startup. Private cancellation records prevent a queued creation from starting after confirmed cleanup. Payload failures retain their exit status; timeout returns 124, Ctrl-C 130 and SIGTERM 143. Collection or unconfirmed cleanup turns an otherwise successful run into failure.
- Transfer deadline fix. An interrupted receive now kills and reaps its child even when stdout has already closed, instead of waiting indefinitely for process exit.
- Retained background jobs.
raft exec --detachreturns a job ID. Usestatus,logsandcancelto manage it. Results and bounded output remain available after the workspace stops or is deleted. - Source sync.
raft synctransfers changed files into an existing workspace, with Git-aware selection and a dry-run option. - Structured output. Global
--jsonemits JSONL events for results, streams, errors and exit codes. - Documentation and verification. A trusted-job GitHub Actions example, package checks and real AMD64/ARM64 tests cover source transfers, failing-command artifacts, timeout, cancellation and template isolation. The static documentation build uses patched Next.js 16.4.1.
Install with npm install -g @microck/raft@0.7.0 or the attached Python wheel. Existing installs can use raft self-update.
Use dedicated hosts and trusted code only. The controller uses existing passwordless-sudo SSH access; it is not a scoped CI identity. Incus boxes share the host kernel and do not provide VM isolation. Templates retain their complete filesystem, including secrets. No credentials, repository secrets, runner registration or paid capacity are provisioned by raft run.
The current expiry worker (protocol 2, introduced in 0.6.0) is required. This release does not change that protocol or configure a retention policy. Host expiry remains a backstop when cleanup cannot be confirmed, not a guarantee of instantaneous deletion or rollback of command side effects.
Verify SHA256SUMS before installing packages or importing the image for your host architecture.