@lingala-composiochecks…session/com-1 → next5 files · +9 −27review: @jkomynoupdated 4d agoThe Composio platform is removing the deprecated V1/V2 UUID-mirror fields from V3 API responses (platform PR #10568, PLEN-2607). The TypeScript SDK read and re-exposed the auth-config uuid — a deprecated mirror of the canonical nanoid id. This PR stops the SDK from depending on the removed field.
transformAuthConfigRetrieveResponse (utils/transformers/authConfigs.ts): drop the uuid: authConfig.uuid mapping.AuthConfigRetrieveResponseSchema (types/authConfigs.types.ts): remove uuid: z.string(). This is a breaking change to the public SDK response type (also affects AuthConfigListResponse items) — consumers should use id instead. Noted in a changeset (minor bump for 0.x).uuid and the deprecated_params / deprecated bags from AuthConfigs/authConfigs.test.ts and test/utils/mocks/data.mock.ts to match the new contract.expectedInputFields investigation (left unchanged)The platform PR removes expected_input_fields only as a member of the deprecated_params bag. In the installed @composio/client@0.1.0-alpha.40 generated types, expected_input_fields?: Array<unknown> still exists as a top-level field on both AuthConfigRetrieveResponse and AuthConfigListResponse.Item, distinct from the nested deprecated_params.expected_input_fields. Since the top-level field survives, the SDK's expectedInputFields read (authConfigs.ts:46) and schema field (types.ts:97) are left in place.
triggers.types.ts authConfigUUID, transformers/triggers.ts) — these come from the Pusher webhook event stream, not the V3 REST responses.deprecated/uuid fields.id; its only uuid usages are the unaffected trigger webhook payloads.pnpm --filter @composio/core build ✅pnpm --filter @composio/core test ✅ (378 tests pass)pnpm lint ✅ (0 errors)🤖 Generated with Claude Code
@lingala-composio is attempting to deploy a commit to the Composio Team on Vercel.
A member of the Team first needs to authorize it.