@devries-cameron20 / composio-1 / commits / 9a51faf57
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.

docs: "latest" requires the skip-version-check flag for manual execution (#4046)

## What Runtime testing during eval-rerun prep caught a docs/runtime mismatch: the guides say `toolkit_versions={"x": "latest"}` works for direct execution, but `tools.execute()` rejects it — ``` ToolVersionRequiredError: Toolkit version not specified. For manual execution of the tool please pass a specific toolkit version. 1. Pass the toolkit version as a parameter to the execute function ("latest" is not supported in manual execution) ... 4. Set dangerously_skip_version_check to True ``` Notably, the [TypeScript SDK reference](/reference/sdk-reference/typescript/tools) already documents the real behavior — the guides contradicted it. An isolated eval agent independently hit the same wall and reported it. Per SDK guidance (@abir-taheer): pass `dangerously_skip_version_check=True` / `dangerouslySkipVersionCheck: true` when running `latest` manually. ## Changes - **All direct-execution samples** (executing-tools, sessions-vs-direct-execution, custom-auth-params, before/after-execution-modifiers) keep `"latest"` and add the skip flag to the execute call with a one-line comment - **executing-tools warning callout** now presents both paths: skip-check when an LLM consumes outputs; pinned version (via `toolkits.get(slug).meta.version`) when code parses them - **toolkit-versioning page**: the "latest is valid" claims are corrected to name the manual-execution requirement - **LLM guardrails** (direct-execution block): same correction — this block is what AI agents copy verbatim - **execute-version static test**: now also fails any page showing `"latest"` in execute samples without the flag (with the runtime evidence cited in the header comment) ## Verification - Both patterns executed against the live API before shipping: `latest` + flag → success; pinned via `toolkits.get(slug).meta.version` (resolved `20260615_00`) → success; `latest` alone → the error above - `bun test tests/static/` — 145 pass; negative check confirmed the new rule fails with an actionable message when the flag is removed - `bun run lint:links` — clean ## Note for reviewer The pinned-version path also returns the *documented* nested response schema — the "flat response" drift agents reported was a base-version (`00000000_00`) artifact. Fixing versioning quietly resolves that report too. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Soumya Medapati committed Aug 3, 2026 at 16:31 UTC 9a51faf5741d7a805728b148b6ab1e395536b5d4

No changes.