+1 (binding), checksums, signatures and licenses look good. (also ran a few
sample requests against breeze instance)

Le lun. 13 nov. 2023 à 23:20, Hussein Awala <[email protected]> a écrit :

> +1 (binding) I tested it by triggering some dag runs and running other API
> requests, and all looks good.
>
> On Tue, Nov 14, 2023 at 12:13 AM Jarek Potiuk <[email protected]> wrote:
>
> > Sorry for missing it for so long.
> >
> > +1 (binding). Checked licences, checksums, signatures, tested that it
> works
> > with latest airflow - following
> >
> >
> https://github.com/apache/airflow-client-python/blob/main/dev/test_python_client.py
> >
> > I also verified sources (finally).
> >
> > One of the things that we do as part of the security improvement work, we
> > are looking at potential holes and improvements in the release process
> and
> > this is one of the things I already realized we should have done - we
> have
> > not generated
> > source code provenience so far for the client - because the source is
> > generated using openapi client.
> >
> > However I figured that it should be as simple as taking the sources of
> > Airflow from the release time and regenerating the client using the same
> > process that the release manager does. Then we could run diff and see if
> > the TAGged sources are the same as the verifying PMC member generated.
> Then
> > (after this is confirmed) - the next step is to compare if the code in
> > packages is the same as in the TAG.
> >
> > I added PR to describe a simple "process" description on how PMC members
> > can verify the sources - which should make our client release process as
> > secure as releasing airflow and providers - because we can be sure the
> > released packages contain code that has not been tampered with.
> >
> > https://github.com/apache/airflow-client-python/pull/101
> >
> > J
> >
> >
> > On Mon, Nov 6, 2023 at 10:45 AM Ephraim Anierobi <
> > [email protected]>
> > wrote:
> >
> > > Hey, fellow Airflowers,
> > >
> > > I have cut the release candidate for the Airflow Python Client
> 2.7.3rc1.
> > > The client consists of APIs corresponding to REST APIs available in
> > > *Apache Airflow 2.7.3*. This email is calling for a vote on
> > > the release, which will last for 72 hours
> > > <
> > >
> >
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=8&iso=20231109T0945&p1=1440
> > > >.
> > > Consider this my (binding) +1.
> > >
> > > Airflow Client 2.7.3rc1 is available at:
> > >
> https://dist.apache.org/repos/dist/dev/airflow/clients/python/2.7.3rc1/
> > >
> > > Or also available at PyPI:
> > > https://pypi.org/project/apache-airflow-client/2.7.3rc1/
> > >
> > > *apache-airflow-client-2.7.3rc1-source.tar.gz* is a source release that
> > > comes with
> > > INSTALL instructions.
> > > *apache-airflow-client-2.7.3rc1-bin.tar.gz* is the binary Python
> "sdist"
> > > release.
> > >
> > > Public keys are available at:
> > > https://dist.apache.org/repos/dist/release/airflow/KEYS
> > >
> > > Only votes from PMC members are binding, but the release manager should
> > > encourage members of the community to test the release and vote with
> > > "(non-binding)".
> > >
> > > *Changelog:*
> > >
> > > *Major changes:*
> > > - NA
> > >
> > > *Major fixes:*
> > > -  Add TriggerRule missing value in rest API #35194
> > > <https://github.com/apache/airflow/pull/35194>
> > > - Fix wrong plugin schema (#34858
> > > <https://github.com/apache/airflow/pull/34858>)
> > >
> > > *New API supported:*
> > > - NA
> > >
> > > Cheers,
> > > Ephraim
> > >
> >
>

Reply via email to