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, 17:15 UTC
chore(deps): remediate Dependabot updates (#4041)
This PR: - consolidates the approved updates from the audited Dependabot queue onto the current `next` branch - refreshes `actions/stale`, development tooling, the Effect family, AI SDK packages, agent frameworks, and runtime support dependencies - migrates the OpenAI runtime to v7 while keeping the published `@composio/openai` peer compatible with v6 and v7 - adds a packed OpenAI 7 and Zod 4 consumer fixture with strict typechecks and offline runtime coverage across Node 22, 24, and 25 - preserves intentional AI SDK 6 and Zod 3 compatibility pins and keeps AG2 as the maintained package - configures Dependabot to skip deliberate compatibility majors, the invalid `@effect/printer-ansi` 1.0.0 target, and Tomli updates blocked by CrewAI - adds release changesets for the published package updates - leaves the AG2 v1 API migration and Tomli/CrewAI update as follow-up work - verifies frozen install, peer policy, changesets, package builds/types/tests, all 20 example typechecks, and production audit; credentialed CLI/Cloudflare E2E remains for CI ## Context The `openai-zod4-compat` fixture deliberately packs `@composio/core` and `@composio/openai` before installing them with npm. Its setup command runs from the fixture directory, so `pnpm --dir /app/ts/packages/core pack` and the equivalent provider command select the source packages while `--pack-destination "$PWD"` writes their tarballs into the fixture. Installing those tarballs instead of using `"@composio/core": "file:/app/ts/packages/core"` exercises the consumer-visible package contents, exports, type declarations, normalized workspace and catalog dependencies, and peer ranges without reusing monorepo links. npm also runs without `--legacy-peer-deps`, ensuring incompatible OpenAI, Zod, core, or provider peer declarations fail the test. The runtime assertions are intentionally offline: they parse a Zod schema, construct OpenAI and Composio clients with a fake `test-key`, verify the OpenAI Responses surface, and wrap tools through both providers without making network requests. A real `COMPOSIO_API_KEY` would add a secret dependency without testing authentication or API behavior, so the fixture no longer passes that environment variable.
No changes.