From a1c3d2871e302b19c16725bce4312604e04b85f5 Mon Sep 17 00:00:00 2001 From: chaodu-agent Date: Thu, 25 Jun 2026 20:08:08 -0400 Subject: [PATCH] build: exclude standalone root crates from the workspace cargo errors with 'current package believes it's in a workspace when it's not' when tooling runs inside a repo-root crate (openab-agent, agy-acp, openab-auth-proxy, operator) that is neither a workspace member nor excluded. This breaks the CI openab-agent job's 'cargo fmt --check' step on the release tag checkout (fails in ~18s before any real checks run). Add these standalone crates to [workspace].exclude. Each has its own Cargo.lock and dedicated CI, so they are intentionally not workspace members. --- Cargo.toml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Cargo.toml b/Cargo.toml index 042ca6223..dd3362ac4 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,5 +1,10 @@ [workspace] members = ["crates/openab-core", "crates/openab-gateway"] +# Standalone crates at the repo root are NOT part of this workspace — each has +# its own Cargo.lock and dedicated CI. Excluding them prevents cargo from +# erroring ("current package believes it's in a workspace when it's not") when +# tooling (e.g. `cargo fmt --check`) runs from inside their directories. +exclude = ["agy-acp", "openab-agent", "openab-auth-proxy", "operator"] [package] name = "openab"