@devries-cameron20 / composio Mirror · read-only
Fork 0

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, 07:15 UTC

next
md 40 lines 1.18 KB
Rendered Raw
1 # Cross-SDK Parity Workflow
2
3 ## Compare The Public Contract
4
5 Check both SDKs for concepts that users experience as equivalent:
6
7 - tools and toolkits
8 - sessions and Tool Router behavior
9 - connected accounts
10 - auth configs
11 - provider wrappers
12 - error shapes and status handling
13 - docs examples and changelog text
14
15 ## Generated Client Bumps
16
17 TypeScript:
18
19 - Verify `npm view @composio/client version`.
20 - Update the catalog pin in `pnpm-workspace.yaml`.
21 - Refresh `pnpm-lock.yaml` with `pnpm install --lockfile-only`.
22 - Add changesets for affected published packages.
23
24 Python:
25
26 - Verify `pip index versions composio-client`.
27 - Update `python/pyproject.toml`.
28 - Update `python/setup.py`.
29 - Refresh root `uv.lock` with `uv lock --upgrade-package composio-client`.
30 - Run an import check such as `uv run --package composio python -c "import composio"` when dependencies are synced.
31
32 ## Naming
33
34 - TypeScript public APIs use camelCase.
35 - Python public APIs use snake_case.
36 - Preserve backend wire names only where generated clients require them.
37
38 ## Verification
39
40 Run the smallest checks that prove both SDKs still expose the intended behavior. Prefer an import/typecheck/test pair over relying on version bumps alone.