Thanks Rahul for preparing the release!
+1 (binding). I have checked,
- SVN
- Reproducible package builds
- Licence
- Signature
- Checksums

Kind regards,
Bugra Ozturk

On Fri, Apr 24, 2026 at 10:20 PM Jens Scheffler <[email protected]> wrote:

> +1 (binding) - Checked SVN, Checksums, Reproducible package build,
> Licenses, Signatures
>
> On 24.04.26 15:37, Jarek Potiuk wrote:
> > +1 (binding)
> >
> > PMC verification:
> >
> > - SVN listing: all 9 files present in dev/airflow/clients/python/3.2.1rc1
> >    (whl + tar.gz + source.tar.gz, each with .asc and .sha512)
> > - SHA512: all 3 checksums match
> > - GPG: all 3 signatures verified — "Good signature from Rahul Vats <
> > [email protected]>"
> > - Reproducible build: built locally from tag python-client/3.2.1rc1 with
> >    `breeze release-management prepare-python-client --use-local-hatch
> > --version-suffix ""`
> >    and `breeze release-management prepare-tarball --tarball-type
> > apache_airflow_python_client
> >    --version 3.2.1 --version-suffix rc1`. diff against SVN files → all 3
> > byte-identical.
> > - Apache RAT 0.18 license check on the source tarball:
> >    Unapproved: 0, Unknown: 0 (Approved: 8629, Standards: 8626).
> >
> > User verification:
> >
> > - `breeze start-airflow --load-example-dags` with basic-auth backend in
> > init.sh,
> >    installed apache-airflow-client==3.2.1rc1 from PyPI inside the
> container,
> > ran
> >    /opt/airflow/clients/python/test_python_client.py — 1 passed in 8.65s.
> >    Exercised: list DAGs, list Tasks, trigger DAG run
> (example_simplest_dag),
> >    read Config. All returned expected models with the new 3.2.1 types
> >    (DAGRunResponse, TaskCollectionResponse, Config).
> >
> > Cheers,
> > Jarek
> >
> > On Fri, Apr 24, 2026 at 2:10 PM Rahul Vats <[email protected]>
> wrote:
> >
> >> Hey fellow Airflowers,
> >>
> >> The release candidate for Apache Airflow Python Client 3.2.1rc1 is now
> >> available for testing!
> >>
> >> This email is calling for a vote on the release, which will last at
> least
> >> 72 hours, from Friday, April 24, 2026 at 12:00  UTC
> >> until Monday, April 27, 2026 at 12:00  UTC
> >> <
> >>
> >>
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20260427T12&p1=1440
> >>> ,
> >> and until 3 binding +1 votes have been received.
> >>
> >> Consider this my (binding) +1.
> >>
> >> Airflow Client 3.2.1rc1 is available at:
> >> https://dist.apache.org/repos/dist/dev/airflow/clients/python/3.2.1rc1/
> >>
> >> The apache_airflow_client-3.2.1.tar.gz is an sdist release that contains
> >> INSTALL instructions, and also
> >> is the official source release.
> >>
> >> The apache_airflow_client-3.2.1-py3-none-any.whl is a binary wheel
> release
> >> that pip can install.
> >>
> >> Those packages do not contain .rc* version as, when approved, they will
> be
> >> released as the final version.
> >>
> >> The rc packages are also available at PyPI (with rc suffix) and you can
> >> install it with pip as usual:
> >> https://pypi.org/project/apache-airflow-client/3.2.1rc1/
> >>
> >> Public keys are available at:
> >> https://dist.apache.org/repos/dist/release/airflow/KEYS
> >>
> >> Only votes from PMC members are binding, but all members of the
> community
> >> are encouraged to test the release and vote with "(non-binding)".
> >>
> >> The test procedure for PMC members is described in:
> >> https://github.com/apache/airflow
> >>
> >>
> /blob/main/dev/README_RELEASE_PYTHON_CLIENT.md#verify-the-release-candidate-by-pmc-members
> >>
> >> The test procedure for contributors and members of the community who
> would
> >> like to test this RC is described in:
> >> https://github.com/apache/airflow
> >>
> >>
> /blob/main/dev/README_RELEASE_PYTHON_CLIENT.md#verify-the-release-candidate-by-contributors
> >>
> >> *Changelog:*
> >>
> >> ## Bug Fixes:
> >> - Fix: use Dag form when materializing asset ([#64211](
> >> https://github.com/apache/airflow/pull/64211)
> >>
> >> Cheers,
> >> Rahul
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to