Hey all,

I have just cut the new wave Airflow Providers packages with release
preparation date 2026-08-01. This email is calling a vote on the
release,
which will last for 72 hours - which means that it will end on
2026-08-06 00:40 UTC and until 3 binding +1 votes have been received.

Consider this my (binding) +1.

This wave contains 48 providers. There are no breaking changes in any
of them - all bumps are minor or patch level.

Four of the providers are re-cuts of release candidates that were
prepared in the 2026-07-22 wave but never published, so they are at
rc2 rather than rc1:

  - apache-airflow-providers-clickhousedb 1.0.1rc2
  - apache-airflow-providers-common-ai 0.7.0rc2
  - apache-airflow-providers-google 22.3.0rc2
  - apache-airflow-providers-openlineage 2.20.0rc2

For those four, the testing status issue carries over the check marks
from the previous wave, so only the genuinely new commits are left
unchecked.

Airflow Providers are available at:
https://dist.apache.org/repos/dist/dev/airflow/providers/2026-08-01

*apache_airflow_providers-2026-08-01-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" distributions that 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/70953

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.1rc1/
https://pypi.org/project/apache-airflow-providers-alibaba/3.4.0rc1/
https://pypi.org/project/apache-airflow-providers-amazon/9.34.0rc1/
https://pypi.org/project/apache-airflow-providers-anthropic/0.2.1rc1/
https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.12.2rc1/
https://pypi.org/project/apache-airflow-providers-apache-hive/9.6.1rc1/
https://pypi.org/project/apache-airflow-providers-apache-kafka/1.15.1rc1/
https://pypi.org/project/apache-airflow-providers-apache-livy/4.6.0rc1/
https://pypi.org/project/apache-airflow-providers-apache-spark/6.3.1rc1/
https://pypi.org/project/apache-airflow-providers-arangodb/2.9.6rc1/
https://pypi.org/project/apache-airflow-providers-celery/3.23.1rc1/
https://pypi.org/project/apache-airflow-providers-clickhousedb/1.0.1rc2/
https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.21.0rc1/
https://pypi.org/project/apache-airflow-providers-cohere/1.6.7rc1/
https://pypi.org/project/apache-airflow-providers-common-ai/0.7.0rc2/
https://pypi.org/project/apache-airflow-providers-common-compat/1.18.0rc1/
https://pypi.org/project/apache-airflow-providers-common-sql/2.1.0rc1/
https://pypi.org/project/apache-airflow-providers-databricks/7.18.1rc1/
https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.9.3rc1/
https://pypi.org/project/apache-airflow-providers-docker/4.5.9rc1/
https://pypi.org/project/apache-airflow-providers-edge3/4.3.0rc1/
https://pypi.org/project/apache-airflow-providers-elasticsearch/6.9.0rc1/
https://pypi.org/project/apache-airflow-providers-exasol/4.10.5rc1/
https://pypi.org/project/apache-airflow-providers-fab/3.8.0rc1/
https://pypi.org/project/apache-airflow-providers-git/0.4.2rc1/
https://pypi.org/project/apache-airflow-providers-google/22.3.0rc2/
https://pypi.org/project/apache-airflow-providers-hashicorp/4.8.0rc1/
https://pypi.org/project/apache-airflow-providers-imap/3.12.1rc1/
https://pypi.org/project/apache-airflow-providers-keycloak/0.9.0rc1/
https://pypi.org/project/apache-airflow-providers-microsoft-azure/14.1.0rc1/
https://pypi.org/project/apache-airflow-providers-neo4j/3.12.1rc1/
https://pypi.org/project/apache-airflow-providers-openai/1.8.2rc1/
https://pypi.org/project/apache-airflow-providers-openlineage/2.20.0rc2/
https://pypi.org/project/apache-airflow-providers-opensearch/1.11.2rc1/
https://pypi.org/project/apache-airflow-providers-papermill/3.13.2rc1/
https://pypi.org/project/apache-airflow-providers-postgres/7.0.1rc1/
https://pypi.org/project/apache-airflow-providers-presto/5.12.1rc1/
https://pypi.org/project/apache-airflow-providers-salesforce/5.14.2rc1/
https://pypi.org/project/apache-airflow-providers-sftp/6.0.1rc1/
https://pypi.org/project/apache-airflow-providers-smtp/3.0.3rc1/
https://pypi.org/project/apache-airflow-providers-snowflake/6.16.0rc1/
https://pypi.org/project/apache-airflow-providers-ssh/6.0.1rc1/
https://pypi.org/project/apache-airflow-providers-standard/1.17.0rc1/
https://pypi.org/project/apache-airflow-providers-telegram/4.9.6rc1/
https://pypi.org/project/apache-airflow-providers-teradata/3.6.2rc1/
https://pypi.org/project/apache-airflow-providers-trino/6.6.1rc1/
https://pypi.org/project/apache-airflow-providers-weaviate/3.4.1rc1/
https://pypi.org/project/apache-airflow-providers-yandex/4.5.1rc1/

Cheers,
Jarek Potiuk

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to