Conversation
…lows
Mirror the funes workflow organization, adapted to agentcap:
- Test - Unit & Integration (test.yml): two jobs — Lint & Unit Tests
(fmt --check, clippy -D warnings, cargo test --lib) and Integration Tests
(cargo test --test proxy, the loopback capture-proxy test). Hermetic; no
protoc/mold/network needed (agentcap, unlike funes, links no protobuf).
- Build - Release (release.yml): compute (conventional-commit version bump on
workflow_dispatch) → build-linux (x86_64) + build-macos (arm64) → publish.
PRs/main build to validate; tag/dispatch publish a GitHub release.
The agent×model end-to-end ("live") tests stay in the existing Python
linux-live-tests.yml until cutover — there are no automated Rust live tests yet.
Both Rust workflows are green locally (fmt/clippy/test + release build).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
CI pins Rust 1.95.0, whose clippy flags `unnecessary_sort_by` on the parquet request enumeration; switch that `sort_by` to `sort_by_key`. Add a rust-toolchain.toml pinning 1.95.0 so local `cargo fmt/clippy/test` matches CI and this drift can't recur. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Rust CI, mirroring the funes workflow organization with more descriptive names.
Workflows
Test - Unit & Integration(test.yml) — hermetic, two jobs (funesci.ymlshape):cargo fmt --check→cargo clippy --all-targets -- -D warnings→cargo test --lib.cargo test --test proxy— the loopback capture-proxy test (mock upstream over127.0.0.1).No protoc / mold / network / podman: agentcap (unlike funes) links no protobuf, and every test here is self-contained.
Build - Release(release.yml) — funesrelease.ymlshape:compute(conventional-commit version bump onworkflow_dispatch) →build-linux(x86_64) +build-macos(arm64) →publish. PRs andmainbuild to validate the release path; a tag or dispatch publishes a GitHub release with the binaries.On "live" vs "integration"
agentcap's heavyweight live tests — build per-agent sandbox images, spawn
llama.cppin podman, drive real agent CLIs — stay in the existing Pythonlinux-live-tests.ymlfor now. There are no automated Rust live tests yet (therunpath was verified by hand across pi/hermes/opencode/goose), so this Rust workflow is deliberately scoped to unit + the hermetic loopback integration test. The Pythonlinux-non-live-tests.yml/linux-live-tests.ymlkeep running until the cutover that removes the Python client.Validated locally
cargo fmt --check,cargo clippy --all-targets -- -D warnings,cargo test --lib(71),cargo test --test proxy(1), andcargo build --releaseall green; both workflow YAMLs parse.🤖 Generated with Claude Code