Releases: outcall-dev/outcall
Releases · outcall-dev/outcall
Release list
v0.1.37
v0.1.36
v0.1.35
v0.1.34
v0.1.33
Release v0.1.33
v0.1.32
Outcall v0.1.32
This patch makes subsequent daemon image releases faster and more reliable.
Release performance
- The multi-architecture daemon build now imports and exports a dedicated
GitHub Actions Buildx cache across release tags. - The cache retains intermediate Rust compilation layers for both Linux
architectures, avoiding unnecessary cold recompilation on later releases. - Cache export failures are non-fatal, so verified release publication still
completes when the cache service is unavailable.
Verification
- The immutable release-tag manifest remains verified before platform archive
export. - The release continues to publish both platform daemon archives and checksums.
v0.1.31
Outcall v0.1.31
This patch repairs deterministic container release tagging.
Release packaging
- The release workflow now explicitly publishes both the immutable release tag
and the rollinglatesttag when it is dispatched frommain. - The workflow verifies the immutable image manifest before exporting platform
archives, so a tag mismatch fails before any release archive work begins.
Verification
- Release builds retain the fast archive export path introduced in v0.1.30:
export each platform from the already-published multi-architecture manifest. - The container job keeps its duration summary and warning threshold so slow
cross-platform builds remain visible in the release run.
v0.1.30
Outcall v0.1.30
This patch makes release packaging and release verification more reliable.
Release packaging
- The release workflow now exports the amd64 and arm64 daemon archives from
the already-published multi-architecture image manifest. It no longer
recompiles the daemon separately for each archive. - Container release jobs publish a duration summary and emit a warning when
image publication plus archive export exceeds 45 minutes.
Verification
- Local installer and secure-runtime CI images are assembled from the
runner-built release binaries and the shared Debian Bookworm runtime stage. - The two jobs use Ubuntu 22.04 so their host-built binaries remain compatible
with the Debian Bookworm runtime image. - Full CI covers local installation, Claude and Codex recipe startup, bridge
isolation, network leak checks, and the secure unattended-mode preflight.
v0.1.29
Outcall v0.1.29
This release makes first-time installation and managed agent runs practical on
macOS Docker Desktop as well as Linux.
First-run workflow
outcall doctor --fix <recipe>starts Docker Desktop when possible, creates
the project scaffold, preloads/checks the daemon runtime, starts the managed
network, and verifies the secure bridge preflight.outcall auth <recipe>stages provider access explicitly.env-onlyuses a
project-local writable home with no copied host credentials;copyand
mountremain available when provider configuration is needed.outcall run <recipe>is the only provider launch command.--namegives a
predictable container name; otherwise concurrent runs are named from the
project folder (<folder>-1,<folder>-2, and so on).outcall ps,outcall logs <name>, andoutcall stop <name>cover the
normal container lifecycle.
Policy workflow
outcall allow codex githubandoutcall allow claude githubadd
recipe-defined grants to the project YAML file.- Exact HTTPS hosts can be granted with
outcall allow codex https://api.sentry.io. outcall policy explain [recipe]shows the active rule file and retains a
default-deny posture for destinations not explicitly allowed.
Installer and verification
- The public installer verifies SHA-256 checksums for the CLI archive and the
daemon image archive before installation. - When Docker is available, it preloads the matching verified Linux daemon
image, avoiding a first-run registry dependency. - macOS uses Docker Desktop's Linux VM for both the daemon and agent runtime.
Verification
- Rust workspace tests and Clippy with warnings denied.
- macOS Docker Desktop end-to-end: repair, auth staging, YAML policy update,
managed Codex launch, named concurrent containers, logs, and stop lifecycle. - Local release-layout installer smoke with SHA-256 verification and daemon
image preload.
v0.1.28
Outcall v0.1.28
This patch makes the explicit first-run command path simpler and fixes repeat
launches in already-initialized projects.
Included changes
- the preferred explicit command is now
outcall run claudeor
outcall run codex - onboarding, installer output, README guidance, and website copy now point at
outcall run <recipe>instead of the older provider aliases outcall run <recipe>is now idempotent on an existing project scaffold
instead of failing on pre-existing generated recipe files- containerized Codex output-file paths now work when the target file lives
inside the mounted project workspace
Verification
- focused Rust tests for:
- onboarding text updates
- idempotent setup on existing recipe files
- workspace output-path rewrite and rejection rules
- macOS end-to-end smoke:
curl -fsSL https://outcall.dev/install.sh | shoutcall doctoroutcall run codex --auth copy -- exec --skip-git-repo-check --ephemeral -o out.txt "Reply with exactly: hi"- repeated
outcall run codex ...on the same project returnedhiagain
and no longer failed on existing scaffold files