CI/CD Pipeline

Outcall uses GitHub Actions for automated checks, release builds, and container image publishing.

Workflows

build-release.yml

Triggered when a version tag (v*) is pushed. Builds release binaries and a multi-arch container image:

Note: outcalld requires Linux for bridge and nftables management. macOS can build the binary, but starting the daemon fails outside Linux.

Each artifact is published to the GitHub Release and accompanied by a SHA256SUMS.txt.

The release also publishes Docker-loadable daemon image archives:

• outcalld-image-linux-amd64.tar.gz
• outcalld-image-linux-arm64.tar.gz

The public installer uses these archives to preload the daemon image during first-time Linux installs when Docker is available.

The container image is pushed to ghcr.io/outcall-dev/outcalld with these tags:

• vX.Y.Z — exact version
• latest — most recent tag

tag-on-merge.yml

Triggered when a PR is merged to main. Automatically increments the patch version (e.g. v0.1.0 → v0.1.1) and pushes the new tag, which in turn triggers build-release.yml.

version-bump.yml

Manual workflow dispatch for minor and major version bumps. Opens a PR that updates version in application/Cargo.toml; on merge to main, tag-on-merge.yml handles the actual tag.

Trigger: GitHub → Actions → Version Bump → Run workflow

Versioning

Each crate carries its own version in its Cargo.toml (e.g. application/outcalld/Cargo.toml). The workspace application/Cargo.toml does not declare a version — the version-bump.yml workflow updates individual crate manifests.

Container Image

Release images are built from application/Dockerfile with multi-arch support for linux/amd64 and linux/arm64.

docker run ghcr.io/outcall-dev/outcalld:latest --version

Secrets

No additional secrets are required for the standard release flow.