CI/CD Guide

Animus uses GitHub Actions for continuous integration and release automation. This guide covers the CI workflows, build commands, and release process.

CI Workflows

Rust Workspace CI (rust-workspace-ci.yml)

Runs on every push and pull request. Checks the workspace and lints with -D warnings:

• cargo check --workspace --all-targets covers every crate (runtime-critical and otherwise) in one cached job — no per-crate matrix to drift against this doc.
• cargo clippy --workspace --all-targets -- -D warnings gates every PR on a clean strict lint (the same gate cargo animus-lint-strict runs locally).
• cargo test --workspace for the full test suite.
• Concurrency grouping cancels superseded runs on the same branch.

Rust-Only Dependency Policy (rust-only-dependency-policy.yml)

Enforces the project rule that Animus is Rust-only -- no desktop shell frameworks (Tauri, Wry, Tao, GTK, WebKit). This workflow rejects PRs that introduce prohibited dependencies.

Web UI CI

The web UI now lives in the external launchapp-dev/animus-web-ui repository and ships its own CI. The Animus monorepo no longer builds or tests the web bundle.

Release Rollback Validation (release-rollback-validation.yml)

Validates that release artifacts can be produced correctly and that the release process is reversible.

Build Commands

Animus provides cargo aliases for building the workspace binaries:

cargo animus-bin-check           # Check all runtime binaries compile
cargo animus-bin-build           # Debug build of all runtime binaries
cargo animus-bin-build-release   # Release (optimized) build

The runtime binary set is:

Binary	Crate	Purpose
animus	orchestrator-cli	Main CLI
agent-runner	agent-runner	Daemon agent runner
animus-oai-runner	oai-runner	OpenAI-compatible runner
animus-workflow-runner	workflow-runner-v2	Workflow phase execution runner (v0.4.x ao-workflow-runner is preserved as a back-compat symlink)

Testing

Run all tests:

cargo test --workspace

Run tests for a specific crate:

cargo test -p protocol
cargo test -p orchestrator-cli
cargo test -p orchestrator-core

Integration tests live in crates/orchestrator-cli/tests/ and cover:

• End-to-end smoke tests
• JSON output contract verification
• Workflow state machine transitions
• Dependency policy enforcement

Release Process (release.yml)

Releases are triggered by pushing a tag matching v* or a branch matching version/**. Manual dispatch is also supported for dry-run validation.

Release Steps

1. Rust gates -- Runs workspace checks and tests for the runtime crates
2. Cross-platform builds -- Compiles release binaries for all targets
3. Packaging -- Creates archives with binaries and metadata
4. Publishing -- Uploads artifacts (for tag pushes, creates a GitHub release)

Build Targets

Target	OS	Runner
x86_64-unknown-linux-gnu	Linux	ubuntu-latest
x86_64-apple-darwin	macOS (Intel)	macos-15-intel
aarch64-apple-darwin	macOS (Apple Silicon)	macos-14
x86_64-pc-windows-msvc	Windows	windows-latest

Creating a Release

Tag and push:

git tag v1.2.3
git push origin v1.2.3

The release workflow builds all targets, packages the archives, and creates a GitHub release with the artifacts.

Local Release Build

Build a release locally:

cargo animus-bin-build-release

Binaries are placed in target/release/ (or target/<triple>/release/ for cross-compilation).