Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 09:45 UTC
chore: bump the owned API client to `2.0.0-rc.13` (#4850)
This PR: - moves `@composio/client` (pnpm catalog and lockfile) and `composio-client` (`python/pyproject.toml`, `python/setup.py`, `uv.lock`) from `2.0.0-rc.12` to `2.0.0-rc.13` - updates the version quoted in `ts/packages/cli/AGENTS.md` - renames the unreleased changeset to `owned-client-rc13.md` so the release notes name the pin that ships, keeping its nullable `id_token` note - limits the `uv.lock` change to the four `composio-client` lines, the same footprint as the rc.12 bump ## Context rc.13 reissues the client after generator and dependency maintenance, with no API change over rc.12 (https://github.com/ComposioHQ/composio-client/pull/79). No runtime behavior changes in either SDK or in the CLI. Verified locally: core and CLI typecheck; `@composio/core` tests (1815 passed, 2 expected failures); CLI tests (1400 passed, 1 skipped); Python tests (2258 passed). Six Python tests fail locally for reasons unrelated to the pin: five need `composio_langchain`, which is not installed in my environment, and the path-join guardrail scans provider `.venv` directories that exist only on my machine. A Bun script run against the live API with the pinned client printed: ```json {"VERSION":"2.0.0-rc.13","toolkits":["gmail","composio","github"],"tool":"GITHUB_GET_A_REPOSITORY"} ```