Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
fix(connected-accounts): accept REVOKED in nested connection-data schema
Codex round 2 caught that the top-level `ConnectedAccountStatusSchema` already accepted REVOKED, but the nested `state.val.status` validation went through `ConnectionStatuses` in `connectedAccountAuthStates.types.ts` which still only knew the prior 6 values. As a result: - `transformConnectedAccountResponse` would silently drop the `state` of any REVOKED account (the discriminated union has no REVOKED variant). - `webhookEvents.types.ts` (which uses `z.nativeEnum(ConnectionStatuses)` for `data.status`) would reject any webhook payload whose top-level account status is REVOKED. Fix: - Add REVOKED to the `ConnectionStatuses` enum (transitively fixes the webhook schema via `nativeEnum`). - Add `Oauth2RevokedConnectionDataSchema` mirroring the Apollo-side schema at `connectionDataScheme.ts` (shape = INITIATING + literal REVOKED status + optional `revoked_at` timestamp), wire it into the `Oauth2ConnectionDataSchema` discriminated union, and export the inferred type. Apollo's PR 9550 only added a REVOKED variant to the OAuth2 scheme; other auth schemes (ApiKey / Basic / Bearer / etc.) do not produce REVOKED at runtime so they don't need a new variant.