@kapa.ai - Are there some compatibility risk with custom connectors developped on previous airbyte version (0.8 for instance) not working with airbyte 1.0 ?

Yes, there are potential compatibility risks when using custom connectors developed for previous Airbyte versions (like 0.8) with newer versions like Airbyte 1.0. Here are some key points to consider: 1. Protocol Version Compatibility: Airbyte has safeguards in place to prevent breaking existing configurations due to protocol version incompatibilities. When upgrading Airbyte, the system checks if currently used connectors will still be supported after the upgrade [Airbyte Protocol Versioning](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol-versioning#safeguards). 2. Upgrade Checks: The

airbyte-bootloader

verifies that connectors used in active connections will be supported after an upgrade. If any connector fails this check, the upgrade is aborted, and you'll need to upgrade those connectors first [Airbyte Protocol Versioning](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol-versioning#safeguards). 3. Connector Upgrades: When upgrading a connector from the UI, Airbyte verifies that the Protocol Version is supported before finalizing the upgrade [Airbyte Protocol Versioning](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol-versioning#safeguards). 4. Custom Connector Issues: There have been reported cases where custom connectors stopped working after Airbyte version updates. For example, a user reported issues with a custom Elastic Search connector after upgrading from version 0.39.42 to 0.40.26 [Custom connector not working anymore after updating Airbyte version](https://discuss.airbyte.io/t/3532). 5. Backward Compatibility Tests: Airbyte includes backward compatibility tests for connectors, but these can be bypassed if necessary [Connector Acceptance Tests Reference](https://docs.airbyte.com/connector-development/testing-connectors/connector-acceptance-tests-reference#test-spec). To mitigate risks: - Test your custom connectors thoroughly after upgrading Airbyte. - Keep an eye on Airbyte's documentation for changes in the Connector Development Kit (CDK) or protocol versions. - Consider reaching out to the Airbyte community or starting a discussion if you encounter issues with custom connectors after upgrades [Contribute a New Connector](https://docs.airbyte.com/contributing-to-airbyte/submit-new-connector#custom-python-cdk-or-java-cdk-connectors).