+1 (binding)
Verified per the PMC checklist in dev/README_RELEASE_PROVIDERS.md
on Linux x86_64 against the artefacts in
https://dist.apache.org/repos/dist/dev/airflow/providers/2026-05-05/.
* SVN check / file inventory — `breeze release-management
check-release-files providers --release-date 2026-05-05` reports
"All expected files are present!"; 105 artefacts confirmed
(17 providers × {.tar.gz, -py3-none-any.whl, .asc, .sha512} +
the source bundle).
* GPG signatures — 35/35 .asc files verify cleanly against KEYS,
all signed by Vincent Beck <[email protected]>
(key 1E7A857875E0EE49DB99E4431B17D6C5938CED00).
* SHA512 checksums — 35/35 match the artefact bytes.
* License (Apache RAT 0.17) on the source tarball — 8806 approved,
0 unapproved, 0 unknown.
* Reproducible build — `breeze release-management
prepare-provider-distributions --include-removed-providers
--distribution-format both` and `prepare-tarball ...
apache_airflow_providers --version 2026-05-05` from the
providers/2026-05-05 git tag (commit 0778210505) produced
byte-identical artefacts to all 35 packages in SVN.
* Smoke install — `docker build Dockerfile.pmc` succeeded;
`airflow info` inside the container lists all 17 providers
at the rcX versions from the vote thread, no import conflicts.
Cheers,
Jarek
On Thu, May 7, 2026 at 10:02 PM Buğra Öztürk <[email protected]>
wrote:
> +1 (binding). I have checked,
> - SVN
> - In Docker installation
> - Reproducible package builds
> - Licence
> - Signature
> - Checksums
>
> Best Regards,
> Bugra Ozturk
>
> On Thu, May 7, 2026 at 8:43 AM Wei Lee <[email protected]> wrote:
>
> > +1 (binding), checked:
> >
> > - SVN
> > - in Docker installation
> > - Reproducible package builds
> > - Licence
> > - Signature
> > - Checksums
> >
> > Best regards,
> > Wei Lee
> >
> >
> >
> > Jens Scheffler <[email protected]> 於 2026年5月7日週四 上午6:22寫道：
> >
> > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package
> build,
> > > Licenses, Signatures
> > >
> > > Did a usual test round with EdgeExecutor and Airflow 3.0.6, 3.1.8,
> 3.2.1
> > > and latest main via Integration test Dag - all looking good!
> > >
> > > On 06.05.26 17:16, Beck, Vincent wrote:
> > > > Hey all,
> > > >
> > > > I have just cut the new wave Airflow Providers packages with release
> > > preparation date 2026-05-05. This email is calling a vote on the
> release,
> > > > which will last for 72 hours - which means that it will end on
> > > 2026-05-09 15:23 UTC and until 3 binding +1 votes have been received.
> > > >
> > > >
> > > > Consider this my (binding) +1.
> > > >
> > > > Airflow Providers are available at:
> > > > https://dist.apache.org/repos/dist/dev/airflow/providers/2026-05-05
> > > >
> > > > *apache-airflow-providers-2026-05-05-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/66480
> > > >
> > > > 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.4.2rc1/
> > > > https://pypi.org/project/apache-airflow-providers-amazon/9.28.0rc1/
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.17.0rc1/
> > > >
> https://pypi.org/project/apache-airflow-providers-common-ai/0.2.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-common-sql/1.36.0rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-databricks/7.14.0rc1/
> > > >
> https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.8.2rc1/
> > > > https://pypi.org/project/apache-airflow-providers-discord/3.12.3rc1/
> > > > https://pypi.org/project/apache-airflow-providers-edge3/3.6.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-fab/3.6.3rc1/
> > > > https://pypi.org/project/apache-airflow-providers-git/0.3.2rc1/
> > > > https://pypi.org/project/apache-airflow-providers-google/21.3.0rc1/
> > > >
> > >
> >
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/13.2.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-mysql/6.5.3rc1/
> > > >
> > https://pypi.org/project/apache-airflow-providers-openlineage/2.16.0rc1/
> > > >
> https://pypi.org/project/apache-airflow-providers-standard/1.13.0rc1/
> > > > https://pypi.org/project/apache-airflow-providers-yandex/4.5.0rc1/
> > > >
> > > > Cheers,
> > > > Vincent Beck
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
>
