+1 (binding): checked files, docker installation, signatures, licences, hashes, reproducible builds, I also ran airflow 3.0.2 with those providers and verified the user creation in FAB is fixed and common.messaging import issue with sqs is also fixed. I am not exactly sure what should be the "/security/login" API - so I have not checked that one (cc Vincent) -but this is not a regression even if it does not work yet.
All looks good! On Fri, Jun 20, 2025 at 6:39 PM Jens Scheffler <j_scheff...@gmx.de.invalid> wrote: > +1 (binding) - Checked SVN, Check in Docker, Reproducible package build, > Licenses, Signatures > > Tested and can confirm that with Fab it is possible w/o workarounds to > create users via UI again. > > On 20.06.25 16:32, Elad Kalif wrote: > > Hey all, > > > > I have just cut the new wave Airflow Providers packages. This email is > > calling a vote on the release, which will last for 72 hours - which means > > that it will end on June 23, 2025 04:30 PM 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/ > > > > *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the binary > > Python "sdist" release - they are also official "sources" for the > Provider > > distributions. > > > > *apache_airflow_providers_<PROVIDER>-*.whl are the binary > > Python "wheel" release. > > > > 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. > > > > The status of testing the providers by the community is kept here: > > https://github.com/apache/airflow/issues/51964 > > > > 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-apache-beam/6.1.1rc1/ > > > https://pypi.org/project/apache-airflow-providers-common-messaging/1.0.3rc1/ > > https://pypi.org/project/apache-airflow-providers-fab/2.2.1rc2/ > > > > Cheers, > > Elad Kalif > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
