Can a custom connector developed with CDK version ^7 can work on the Airbyte platform v 2.0.1 ?

Thinking completed The knowledge sources do not explicitly mention compatibility details between CDK v7 connectors and Airbyte platform v2.0.1. I can share what the sources do tell us, but I cannot give a definitive compatibility confirmation. What the knowledge sources indicate: • Airbyte platform v2.0.1 (released October 22, 2025) only notes an "optimized heartbeat mechanism" in its release notes — no CDK compatibility information is mentioned. [v2.0.1 release notes] • CDK v7 connectors are actively being developed and merged into the Airbyte connector catalog (e.g., source-posthog, source-adjust, source-jina-ai-reader all recently upgraded to CDK ^7). [CDK v7 upgrade] [CDK v7 adjust] • Custom connectors on Airbyte work by packaging them as Docker images that implement the Airbyte Protocol. As long as your connector image correctly implements the protocol (spec, check, discover, read/write), it can be registered and used in Airbyte regardless of which CDK version was used to build it. [custom connectors] [Airbyte Docker Protocol] In practice: Since CDK v7 connectors are being actively merged and used in the Airbyte ecosystem, and custom connectors are decoupled from the platform version (they run as Docker containers implementing the Airbyte Protocol), a CDK v7-based custom connector should work on Airbyte v2.0.1 — provided the connector correctly implements the Airbyte Protocol. However, I'd recommend verifying this directly with the Airbyte community or documentation, as the knowledge sources don't explicitly confirm this compatibility pairing. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.