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, 23:30 UTC
docs: add guidance on when to use latest vs pinned toolkit versions (#3207)
# Description Replaces the blanket "never use `latest` in production" advice with nuanced guidance based on how tool outputs are consumed: - **Use `latest`** when tool outputs and trigger payloads are consumed by an LLM or AI agent (agentic consumption) — agents interpret responses dynamically and adapt to schema changes - **Pin a specific version** when tool outputs are parsed programmatically (schematic consumption) — e.g., destructuring fields, mapping to a database schema, or feeding into typed pipelines Updated across 6 pages: - **`toolkit-versioning.mdx`** — New "Choosing between `latest` and a pinned version" section replaces the old "never use latest in production" warning - **`changelog/04-08-26-v31-api.mdx`** — Added "which default is right for you" to the migration guide - **`common-faq.mdx`** — Expanded toolkit versioning FAQ with agentic vs schematic recommendation - **`sessions-vs-direct-execution.mdx`** — Added "Version management" row to the comparison table - **`executing-tools.mdx`** — Added version strategy callout in direct execution section - **`creating-triggers.mdx`** — Expanded trigger versioning note to explain why `latest` is the default # How did I test this PR - Verified all 6 files have clean diffs with `git diff` - Checked that internal links point to valid anchors (`#choosing-between-latest-and-a-pinned-version`) - Confirmed branch is based on latest `next`
No changes.