Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
fix(cli): ship every codex-acp binary in release archives (#4186)
## Problem `composio upgrade` fails on every CLI currently in the field, including stable `0.3.3`: ``` 💥 services/UpgradeBinaryError • Downloaded binary package is incomplete Caused by: Missing companion module: …/extract/composio-darwin-aarch64/acp-adapters/codex/darwin-x64/codex-acp ``` `archiveCompanionRelativePaths` (added 2026-08-18 in #4134) narrows each release archive to the shared ACP assets plus only the one `codex-acp` its platform can execute. That is a sound optimisation, but it shipped writer-first: a CLI released *before* it verifies a downloaded package against `RUN_COMPANION_STATIC_ASSET_RELATIVE_PATHS` — shared assets plus **all four** codex target paths — with no parameter to relax the check, and hard-fails on any archive missing one. Stable `0.3.3` shipped 2026-08-11, a week before that change, so the entire installed stable base is affected. Recovery today means re-running `install.sh` by hand. Evidence: | Archive | codex binaries shipped | | --- | --- | | `0.3.4-beta.351` (pre-#4134) | `darwin-arm64`, `darwin-x64`, `linux-arm64`, `linux-x64` | | `0.4.0-beta.357` (post-#4134) | `darwin-arm64` only | ## Fix The reader has to become tolerant before the writer narrows, and the already-installed reader cannot be patched retroactively. Packaging ships the full companion set again. `archiveCompanionRelativePaths` stays in place with its tests, documented as deliberately uncalled. Re-wiring it into `package-binaries.ts` is a one-line change once no supported client still validates all four paths — worth roughly 651 MB per archive. ## Why CI missed it `cli.test-installation.yml` only exercises fresh `install.sh` installs, which are unaffected: each archive is internally consistent. Nothing covers an in-place upgrade from a previously released binary. Worth closing separately — it needs a real prior-stable binary in the matrix, not a unit test. ## Verification - `vitest run test/src/scripts/release-artifacts.test.ts` — 29 passed - `pnpm --filter @composio/cli typecheck` — clean - `pnpm validate:changesets` — passes (CLI is Changesets-ignored; note lands in `ts/packages/cli/CHANGELOG.md`) - Added coverage asserting every release artifact's codex-acp binary is in the packaged set - Final check is the archive itself: the beta cut from this branch must contain all four `acp-adapters/codex/*/codex-acp` entries, and `composio upgrade` must succeed from a pre-#4134 install `@composio/cli@0.4.0-beta.357` should be abandoned rather than promoted. https://claude.ai/code/session_01JkwtxPHfobZxzvAqe53x62