Thanks Jarek for preparing the release.

+1 (binding), checked:

- SVN
- in Docker installation
- Reproducible build
- Licence
- Signature
- Checksums

Regards,
Pavan

On Sat, Aug 8, 2026 at 3:16 AM Jarek Potiuk <[email protected]> wrote:

> Hey all,
>
> I have just cut a wave of Airflow Providers packages with release
> preparation
> date 2026-08-08. This email is calling a vote on the release, which will
> last
> for 24 hours - which means that it will end on 2026-08-09 02:10 UTC and
> until
> 3 binding +1 votes have been received.
>
> Consider this my (binding) +1.
>
> This vote runs in parallel with the still-open vote on the 2026-08-06 wave.
> The two waves are disjoint and this is the first time we have the case
> where
> we run two provider votes in parallel (we can do it as of recently) -
> good way to
> test if this works. No provider appears in both - so a vote on one
> does not affect the other. This wave contains the two providers that were
> pulled out of 2026-08-06:
>
>   - apache-airflow-providers-google 22.3.0rc4
>     Removed from 2026-08-06 on a binding -1: the provider did not install
> on
>     Python 3.14. That turned out to be a dependency problem in
>     google-cloud-aiplatform's "evaluation" extra, reported upstream as
>     googleapis/python-aiplatform#7057 and worked around in
>     https://github.com/apache/airflow/pull/71273 by requiring the extra's
>     dependencies directly. Tracked in
>     https://github.com/apache/airflow/issues/71268.
>
>   - apache-airflow-providers-cncf-kubernetes 10.21.0rc3
>     Removed from 2026-08-06 because the two new concurrent-pod-creation
>     options declared "version_added: 10.20.0" when they actually ship in
>     10.21.0. Fixed in https://github.com/apache/airflow/pull/71157.
>
> Both providers were cut as release candidates but never published, so their
> versions are unchanged - 22.3.0 and 10.21.0 - and their changelog sections
> were extended rather than superseded.
>
> There are no breaking changes in either provider; both bumps are minor
> level.
>
> Because both are re-cuts, most of the testing from the 2026-08-06 wave
> still
> applies: only the two changes listed above are new. The testing status
> issue
> for this wave is
> https://github.com/apache/airflow/issues/71321
>
> Airflow Providers are available at:
> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-08-08
>
> *apache_airflow_providers-2026-08-08-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 all 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 packages released to PyPI, with their rc suffixes:
>
>
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.21.0rc3/
> https://pypi.org/project/apache-airflow-providers-google/22.3.0rc4/
>
> J.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to