Hello everyone, I wanted to ask for a lazy consensus on suspension of Yandex provider due to its protobuf 4 limitation that we are currently actively working on removing.
I prepared a PR to do so: https://github.com/apache/airflow/pull/30667 and you can read more about consequences of suspension in https://github.com/apache/airflow/blob/main/README.md#suspending-releases-for-providers Below is a copy of the justification for the suspension from the PR. No need to vote on it, lack of binding dissent is enough for lazy consensus to be effective. The lazy consensus will be open till Wednesday 11 am CEST, 19th of April. J. --------------- Copy of the justification from https://github.com/apache/airflow/pull/30667 Yandex provider brings protobuf dependency down to <4 and we are gearing up to updating it everywhere else. Protobuf3 support ends in Q2 2023 for Python https://protobuf.dev/support/version-support/#python Yandex is the last provider that we do not closely collaborate with on fixing it. * Gogle provider dependencies are actively upgraded to latest version by Google led team: Update SDKs for google provider package https://github.com/apache/airflow/pull/30067 (some of the libraries are already updated) with target to update all dependencies by mid-May * Apache-Beam has already merged protobuf4 support Bump google.golang.org/protobuf from 1.29.0 to 1.30.0 in https://github.com/apache/beam/pull/25874 with the target of releasing it in 2.47.0 mid-May * The mysql-connector-python in MySQL provider is already turned into optional dependency: Remove mysql-connector-python https://github.com/apache/airflow/pull/30487 The only remaining dependency limiting us to protobuf 3 (<3.21) is yandexcloud. We've opened an issue to yandexcloud https://github.com/yandex-cloud/python-sdk/issues/71 3 weeks ago and while there was an initial interest, there is no progress on the issue, therefore - in order to prepare for running all the tests and final migration to protobuf4 we need to suspend Yandex provider - following the suspension process we agreed and got a LAZY CONSENSUS on in the https://lists.apache.org/thread/g8b3k028qhzgw6c3yz4jvmlc67kcr9hj mailing list discussion. The yandex provider can be removed from suspension by a PR reverting this change once yandexcloud dependency removes the protobuf limitation in their release and PR reverting this change (and fixing all tests and static check that will be needed) is the way it can be done. J.
