+1 (non-binding)

Le lun. 16 janv. 2023 à 13:23, Ephraim Anierobi <ephraimanier...@apache.org>
a écrit :

> Hello everyone,
>
> I have cut the first release candidate for the Airflow Python Client 2.5.0.
> The client consists of APIs corresponding to REST APIs available in
> *Apache Airflow 2.5.1* release candidate. This email is calling for a vote
> on
> the release, which will last for 72 hours. Consider this my (binding) +1.
>
> Airflow Client 2.5.0.rc1 is available at:
> https://dist.apache.org/repos/dist/dev/airflow/clients/python/2.5.0rc1/
>
> Or also available at PyPI:
> https://pypi.org/project/apache-airflow-client/2.5.0rc1/
>
> *apache-airflow-client-2.5.0rc1-source.tar.gz* is a source release that
> comes with
> INSTALL instructions.
> *apache-airflow-client-2.5.0rc1-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*
>
> *Bug fixes*
>
> - FIX Make items nullable for TaskInstance related endpoints to avoid API
> errors (#26076)
>
> - Fix response schema for list-mapped-task-instance (#25965)
>
>
> *New features*
>
> - Add map index to task logs api (#25568)
>
> - clear specific dag run TI (#23516)
>
> - Sync up plugin API schema and definition (#25524)
>
> - Add and document description fields (#25370)
>
> - Add `uri_pattern` query param to Get `/datasets` endpoint (#25411)
>
> - Add URI to dataset event response (#25250)
>
> - Add .../dagRuns/DR-ID/upstreamDatasetEvents endpoint (#25080)
>
> - Add dataset events to dataset api (#25039)
>
> - Add read-only REST API endpoint for Datasets (#24696)
>
> - Add is_mapped field to Task response. (#23319)
>
> - Add clear DagRun endpoint. (#23451)
>
> - Add support for queued state in DagRun update endpoint. (#23481)
>
> - Add fields to dagrun endpoint (#23440)
>
> - Add is_mapped field to Task response. (#23319)
>
>
> Cheers,
>
> Ephraim & Pierre
>
>

Reply via email to