Excluding clickhousedb from the vote (-1 binding), changes are only to its
provider's metadata.


Shahar

On Fri, Jul 24, 2026 at 8:00 AM Shahar Epstein <[email protected]> wrote:

> Hey all,
>
> I have just cut the new wave Airflow Providers packages with release
> preparation date 2026-07-22. This email is calling a vote on the release,
> which will last for 72 hours - which means that it will end on 2026-07-27
> 05:00 UTC and until 3 binding +1 votes have been received.
>
> Consider this my (binding) +1.
>
> Breaking changes in the current RC:
>
> - Airbyte 6.0.0rc1: upgraded to airbyte-api 1.x and switched underlying
> HTTP client from requests to httpx. Most Dag-level interfaces stay the
> same, but environments relying on transitive dependencies must adapt
> (explicitly depend on requests if needed, and direct airbyte_api consumers
> need to handle 1.x/Pydantic request model behavior).
> - Microsoft Azure 14.0.0rc1: minimum azure-mgmt-datafactory bumped from
> 2.x to 10.x due to upstream SDK breaking changes. Airflow hook API remains
> compatible, but runtime environment must upgrade azure-mgmt-datafactory to
> >=10.0.0 (or remain on provider 13.x).
> - Postgres 7.0.0rc2: default Postgres drivers switch to psycopg3 for both
> sync and async paths on Airflow 3.4+. Async default URL effectively changes
> from postgresql+asyncpg:// to postgresql+psycopg_async:// unless explicitly
> pinned. Users wanting old behavior should set connection URLs explicitly to
> psycopg2/asyncpg.
> - SFTP 6.0.0rc1: paramiko minimum bumped to 4.0.0; DSS/DSA keys are no
> longer supported. Users with DSA/DSS keys or ssh-dss host key pinning must
> rotate to supported key types (for example Ed25519/RSA).
> - SSH 6.0.0rc1: same paramiko 4.0.0 impact as above; DSA private keys and
> ssh-dss host keys are unsupported and require key migration.
>
> Airflow Providers are available at:
> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-07-22
>
> *apache-airflow-providers-2026-07-22-source.tar.gz* is the full source
> tarball of airflow repo - snapshot taken at the moment of provider's
> release.
>
> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience python
> "sdist" distributions that we publish in PyPI
>
> *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> "wheel" distributionsthat we publish in PyPI.
>
> The test procedure for PMC members is described in
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members
>
> The test procedure for and Contributors who would like to test this RC is
> described in:
>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors
>
>
> Public keys are available at:
> https://dist.apache.org/repos/dist/release/airflow/KEYS
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Only votes from PMC members are binding, but members of the community are
> encouraged to test the release and vote with "(non-binding)".
>
> Please note that the version number excludes the 'rcX' string.
> This will allow us to rename the artifact without modifying
> the artifact checksums when we actually release it.
>
> The status of testing the providers by the community is kept here:
> https://github.com/apache/airflow/issues/70355
>
> The issue is also the easiest way to see important PRs included in the RC
> candidates.
> Detailed changelog for the providers will be published in the
> documentation after the
> RC candidates are released.
>
> You can find the RC packages in PyPI following these links:
>
> https://pypi.org/project/apache-airflow-providers-airbyte/6.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-akeyless/0.3.0rc1/
> https://pypi.org/project/apache-airflow-providers-amazon/9.33.0rc1/
> https://pypi.org/project/apache-airflow-providers-anthropic/0.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-hive/9.6.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-kafka/1.15.0rc1/
> https://pypi.org/project/apache-airflow-providers-apache-spark/6.3.0rc1/
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/3.3.5rc1/
> https://pypi.org/project/apache-airflow-providers-celery/3.23.0rc1/
> https://pypi.org/project/apache-airflow-providers-clickhousedb/1.0.1rc1/
>
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-ai/0.7.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-compat/1.17.0rc1/
> https://pypi.org/project/apache-airflow-providers-common-sql/2.0.3rc1/
> https://pypi.org/project/apache-airflow-providers-databricks/7.18.0rc1/
> https://pypi.org/project/apache-airflow-providers-docker/4.5.8rc1/
> https://pypi.org/project/apache-airflow-providers-edge3/4.2.0rc1/
> https://pypi.org/project/apache-airflow-providers-elasticsearch/6.8.1rc1/
> https://pypi.org/project/apache-airflow-providers-fab/3.7.3rc1/
> https://pypi.org/project/apache-airflow-providers-google/22.3.0rc1/
> https://pypi.org/project/apache-airflow-providers-hashicorp/4.7.2rc1/
> https://pypi.org/project/apache-airflow-providers-http/6.0.5rc1/
> https://pypi.org/project/apache-airflow-providers-keycloak/0.8.2rc1/
>
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/14.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-openai/1.8.1rc1/
> https://pypi.org/project/apache-airflow-providers-openlineage/2.20.0rc1/
> https://pypi.org/project/apache-airflow-providers-opensearch/1.11.1rc1/
> https://pypi.org/project/apache-airflow-providers-pgvector/1.7.3rc1/
> https://pypi.org/project/apache-airflow-providers-postgres/7.0.0rc2/
> https://pypi.org/project/apache-airflow-providers-sftp/6.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-snowflake/6.15.0rc2/
> https://pypi.org/project/apache-airflow-providers-ssh/6.0.0rc1/
> https://pypi.org/project/apache-airflow-providers-teradata/3.6.1rc1/
> https://pypi.org/project/apache-airflow-providers-weaviate/3.4.0rc1/
>
>
> Sincerely,
>
>
> Shahar
>

Reply via email to