Hey all,

I have just cut a RC2 of the wave Airflow Providers packages with release preparation date 2026-05-25. This email is calling a vote on the release, which will last for 24 hours - which means that it will end on 2026-05-26 19:23 UTC and until 3 binding +1 votes have been received. This is a shortened (24 hours vote) as agreed by policy set it https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm

Consider this my (binding) +1.

Reason for the release cut are the bugs found during testing with Airbyte and dbt-clout provider which are now fixed in RC2. No other change and just 2 providers re-released.

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

 * apache-airflow-providers-2026-05-25-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/67490

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/5.5.0rc2/
https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.9.0rc2/

Cheers,
Jens Scheffler

Reply via email to